Customer Service Jobs API
Pricing
from $0.80 / 1,000 job records
Customer Service Jobs API
Find customer service and call center job postings worldwide by role, location, company, salary, posting age, employment type, remote status, and seniority.
Pricing
from $0.80 / 1,000 job records
Rating
0.0
(0)
Developer
Aspen Technology Labs, Inc.
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Customer Service / Call Center Jobs API - JobsIndex by Aspen Tech Labs
This Actor provides direct access to customer service and call center job openings from employers worldwide. Because these roles are commonly hired remotely or through outsourced BPO providers, companies recruit for them across the globe. The dataset currently covers 200,000+ live vacancies across more than 22,000 employers internationally.
Hiring is concentrated in major outsourcing hubs in Latin America, led by Santiago, Chile, followed by Lima, Peru, and Bogota, Colombia. Other leading cities include Athens, New York, Lisbon, Medellin, London, and Bengaluru. Postings retain local context: alongside "Customer Service Representative," the dataset includes raw titles such as Agent d'Accueil from French employers and Kundenberater from German employers.
The dataset covers two closely related sub-categories: Customer Service Representative, with approximately 175,000 open roles, and Call Center Representative, with approximately 28,000. Titles range from customer service representative, call center representative, client service representative, customer support representative, and client care representative to more specialized roles such as customer experience representative, service desk representative, automotive service advisor, and member service representative. It also includes team-lead, management, and senior client-facing roles such as customer service leader, customer success representative, customer service executive, head of customer success, VP of client onboarding, and director of client relationships.
Employers include major US retail and consumer brands such as Dollar Tree, Domino's, Home Depot, Walgreens, Costco, and State Farm; international organizations such as LVMH, Sparkasse, Tata Capital, Standard Chartered, and Tesco; and call-center and BPO providers such as Konecta, Atento, Emtelco, and MCI.
Use this Actor to source live customer service and call center roles for job boards or recruiting tools, track which BPO providers and direct employers are actively hiring, or analyze where hiring is concentrated globally, city by city.
Need More or Something Different?
If this Actor is working well for you, we'd love a review. For more data, custom feeds, feedback, or questions, reach out through our website or by email. You can also explore JobMarketPulse, our labor and job market intelligence platform.
Built-In Search Preset
This Actor always retains an internal customer-service preset covering the JobsIndex Customer Service Representative and Call Center Representative classifications. The preset itself is not editable in the Actor UI.
The user-facing what field does not replace the preset. When a user enters what, the Actor appends the role query to the internal customer-service query with AND and searches it across job title and job-family fields.
For example, user input:
{"what": "bilingual OR manager","where": "Germany OR France","remote": "remote","size": 5}
keeps the customer-service preset and further narrows it to matching bilingual or manager roles. If what is empty, the Actor sends only the internal customer-service preset.
Quick Start
{"what": "bilingual OR manager","country": "United States","remote": "remote","size": 5}
Input Parameters
| Parameter | Description | Example |
|---|---|---|
salary | Salary amount or range filter. | 20h-30h |
what | Optional role search within the customer-service dataset. The Actor appends it to the internal preset with AND. | bilingual OR manager |
where | Optional free-text location search with place names, boolean logic, or field targeting. | Germany OR France |
country | Country filter. | United States |
region | State, province, or region. | Texas |
city | City filter. | Austin |
postal_code | Postal or ZIP code filter. | 78701 |
metro_area | Metropolitan area filter. | Austin-Round Rock-San Marcos, TX |
title | Job title filter. | Customer Service Manager |
company_name | Company name filter. | Concentrix |
company_domain | Company website domain. | concentrix.com |
category | Job category filter. | Retail |
sub_category | More specific customer service role group. | Customer Service Representative |
industry | Company industry filter. | Business Services |
posted | Relative posting age or ISO date. | 1w |
employment_type | Employment type. | Full-Time |
remote | Work arrangement filter. Supported values: remote, on-site, hybrid. | remote |
seniority | Seniority level. | Manager |
page | Page number, starting from 0. | 0 |
size | Number of results per page. Default 5, min 1, max 100. | 5 |
Search Behavior
The Actor's internal customer-service preset is always retained. User input in what is appended with AND and searched across:
titletitle_rawcategorysub_category
Examples:
what = bilingualwhat = manager OR supervisorwhat = customer successwhat = technical support
Use what for a free-text role search. Structured job fields such as title, company_name, company_domain, category, sub_category, industry, posted, salary, employment_type, remote, and seniority can further narrow the result set.
Use where for free-text location searches, boolean location expressions, or field-targeted location queries:
where = Germanywhere = Germany OR Francewhere = @(country) (Germany OR France)where = @(city,metro_area) (London)
where is independent from the Actor's enforced customer-service what preset. Using where does not replace the preset or the optional user-facing what query.
Structured Filter Precedence
Use where when the structured location filters are not set. If where is provided together with country, region, city, postal_code, or metro_area, those structured filters take priority and can override, narrow, or deprioritize where.
Salary Filter Format
Use NUMBER[UNIT] or NUMBER[UNIT]-NUMBER[UNIT].
Supported units:
h- per hourd- per dayw- per weekm- per monthy- per year
Examples:
20h-30h- hourly rate between 20 and 3050000y- yearly salary of 50,00040000y-70000y- yearly salary range
Location Filtering
This is a global Actor. Use where or the structured location filters below to narrow results:
countryregioncitypostal_codemetro_area
Limits and Pagination
This Actor uses the JobsIndex jobs API. Results are paginated with page and size.
| Parameter | Default | Min | Max |
|---|---|---|---|
page | 0 | 0 | Depends on size and the item cap |
size | 5 | 1 | 100 |
Invalid page or size values can return 400 Invalid page or size parameters.
Item Caps
| Query shape | Max items | Effective max size | Over-size behavior |
|---|---|---|---|
| No company filter | 1000 | 100 | Validation error; not silently capped |
| Company filter with the Actor preset or another filter | 20 | 20 | Silent cap with capping metadata |
A company filter means company_name or company_domain. This Actor always applies an internal customer-service query, so company-filtered requests use the 20-item cap.
When capping applies, response metadata includes size_requested and size_capped_by="company|keywords". These fields are absent from uncapped responses.
No-company-filter requests are not silently capped. Requests beyond the 1000-item retrieval window can return 400 Item limit reached. Maximum of 1000 items can be retrieved.
Free-Text Query Limits
The optional user-facing what and where queries are each subject to JobsIndex free-text limits:
| Limit | Value | Error behavior |
|---|---|---|
| Raw URL length before decoding | 700 characters per parameter | 400 parameter exceeds 700 characters |
| Decoded text length | 500 characters per parameter | 400 MATCH input exceeds length limit |
Combined operator characters: ?, +, pipe, @ | 20 per parameter | 400 Too many MATCH operators |
| Unsafe SQL-like keywords | blocked | 400 Unsafe MATCH expression |
Field Validation
Invalid filter values can return 400 Invalid value for parameter: <name>. Common validation examples include malformed company domains, invalid dates or relative posted values, invalid salary format, unsupported location formats, or overly long field values.
Output
Each run stores job records in the default Apify dataset. The dataset schema includes an Overview table for the most useful fields and a Raw data (all fields) table for the complete JobsIndex record.
Example dataset item:
{"id": "9343167339286732210","title": "Customer Service Representative","title_raw": "Customer Service Associate I","company_name": "ABC Hidden Co","company_domain": "hidden.sample.com","category": "Retail","sub_category": "Customer Service Representative","country": "United States","region": "Colorado","city": "Westminster","metro_area": "Denver-Aurora-Centennial, CO","salary_value": "20.00","salary_currency": "USD","salary_unit": "HOUR","employment_type": "Part-Time","posted": "2025-12-12","url_source": "https://hiddenats.sample.com/abchiddenco/job/Customer-Service-011119"}
Field availability depends on the source job posting.