Direct integrations for Sponsored Jobs API reference
2026-01-08: Sponsored Jobs API usage policy (US): as of 2024-12-01, Sponsored Jobs API customers pay for API usage based on their sponsorship spend. The policy does not apply to users of Indeed's proprietary ATS plugin. For recommended API usage patterns, see Sponsored Jobs API best practices to reduce call volume. 2026-01-08: Sponsored Jobs API usage policy: as of 2026-02-01, per-call charges apply in these markets: EU markets and Switzerland (AT, BE, CH, DE, DK, EE, ES, FI, FR, GR, IE, IT, LU, NL, PL, PT, RO, SE): 3 EUR, or the equivalent in the advertiser's billing currency. Other markets (AR, AU, BR, CA, CL, CO, CR, GB, ID, IN, MX, MY, NZ, PA, PH, SG, TH): 3 USD, or the equivalent in the advertiser's billing currency. Fees apply only when your monthly Sponsored Jobs campaign spend is less than your monthly API call cost. The policy applies to all paying Sponsored Jobs API customers except users of Indeed's proprietary ATS plugin. Eligibility: You can use the Sponsored Jobs API only if you sponsored a job in the last three calendar months. Monthly call limit: The maximum is the greater of: Monitor your usage: Call For recommended API usage patterns, see Sponsored Jobs API best practices to reduce call volume. Sponsored Jobs API usage policy
/apiquotausage to retrieve your current month's API usage.
View and manage an employer's sponsored jobs.
Additional migration note
#This response field is deprecated and the API no longer returns it:
budgetOptimizationTargetfield returned fromGET /v1/campaigns/{campaignId}/budget
This response field is in the process of being deprecated:
AveragePagefield returned fromGET /v1/campaigns/{campaignId}/statsandGET /v1/campaigns/{campaignId}/stats/{date}
Client apps do not receive these fields. Make sure your app does not expect deprecated fields to be present in responses.
Authorization
#To authorize your app to act on behalf of itself or the Indeed employer accounts of your customers, use the client credential grant type (2-legged OAuth). This grant type does not require user interactions to authorize access.
To act on behalf of an employer, call the Sponsored Job Campaigns API with an employer access token.
Agencies and programmatics
If you are an agency that uses programmatics services to integrate with APIs, consider setting up the programmatic as a secondary user for each employer account that the programmatic is managing. Then, programmatics can use the Client credential grant type (2-legged OAuth) to access your account and carry out campaign related actions. Secondary users coupled with OAuth are the industry standard for delegating access. Avoid credential sharing, which has many pitfalls.
OAuth scopes
#When requesting an OAuth access token, your app must request OAuth scopes, which determine the level of access the client grants your app. For details, see Sponsored Jobs API scopes. These scopes are also included in each endpoint below.
Secondary users
#The primary user sets up an employer account at Indeed. This user has full access to all resources associated with the employer account at Indeed. Primary users can give others access to their employer account. These additional users are called secondary users. Primary users can add and view secondary users and their permissions from their Indeed Account （新しいウィンドウで開きます） page.
Rate limiting
#Indeed applies rate limiting to this API. This ensures system stability against unauthorized or unexpected use.
Eventual consistency
#The API is expected to adopt an eventual consistency model. For example, when you call the POST /v1/campaigns campaign creation endpoint to create a campaign, a call to GET /v1/campaigns/{campaignId} might not return the new campaign for a brief time. See Prepare for eventual consistency in the Sponsored Jobs API get started.
Compatibility with API changes
#Backwards-compatible changes to the Sponsored Jobs API can be released at any time and without prior notice. Changes considered backwards-compatible include:
- Add response fields.
- Reordering response fields.
- Changing descriptions of errors.
- Supporting new currencies and objective types.
To learn how to avoid issues caused by API changes, see Ensure compatibility with API changes.
Campaign dates
#In the campaigns endpoint, dates are in US Central Time and should follow the ISO 8601 standard with a format of YYYY-MM-DD.
The campaign date fields are:
startDateUse the current date or a later date. If you do not provide a date, the default is the current date.
targetEndDate:A campaign can have only one end date:
targetEndDateorfixedEndDate.targetEndDatemust be at least one day after the start date. If set, Indeed optimizes spending by this date, but the campaign can continue spending after it if budget remains.fixedEndDate:A campaign can have only one end date:
targetEndDateorfixedEndDate.fixedEndDatemust be at least one day after the start date. If set, Indeed optimizes spending by this date and does not spend after it, even if budget remains.
Campaign traffic statistics
#Campaign traffic statistics are available from January 1st, 2017.
Organic clicks and organic impressions
#Starting 2020-08-23, Indeed made organic clicks and organic impressions traffic statistics available. See the updated endpoints in the Reports and Detailed Reports sections. Organic metric data backdates to January 1st, 2017.
Search engine results page count
#Starting 2020-04-01, Indeed changed the methodology for counting Search Engine Results Pages (SERP) impressions for some services. All impressions in the SERP are now counted when they are made visible to the user. This change speeds up the availability of certain performance metrics. The good news for you is that this helps:
- Deliver non-Sponsored jobs data much faster than before.
- Offer consistency on desktop and mobile reporting.
Average daily budget (ADB) campaigns
#Matched Candidates for Premium campaigns is not available through these endpoints:
Advertisers still receive this benefit, but they must sign in to the Indeed UI to use it.
These Premium benefits are included in the Premium package, subject to job eligibility:
- Matched Candidates
- Urgently Hiring tags
- Job Branding
- First Page Boost
- Expanded Reach
- AI tools
- Location Targeting
- Advanced Matching
Conversion Tracker sunset
#Indeed sunset the Conversion Tracker effective 2021-10-01. As a result, Conversion Tracker data is not collected or displayed after October 1, and historical data is available until October 1, 2022. You might see lower conversions being reported effective 2021-10-01.
Objective-based campaigns
#The Sponsored Jobs API supports objective-based campaigns. See Reach Your Recruiting Goals With Objective Based Campaigns （新しいウィンドウで開きます）. You cannot set or change objectives for average daily budget (ADB) campaigns. All other Sponsored Jobs API campaigns must have an objective. If the employer does not provide one when creating a campaign, Sponsored Jobs API selects an appropriate objective automatically.
Note: Some objectives rely on the availability of app metrics. If you are not sure of the availability of app metrics, talk to your client success specialist to explore other solutions.
Endpoints
#Endpoints that support objective-based campaigns are:
POST /v1/campaignsGET /v1/campaigns/{campaignId}PATCH /v1/campaigns/{campaignId}
Release dates
#2021-09-02
#- Scheduled interviews – optimize for the number of interviews
2021-12-07
#- Target a specific cost per apply
- Maximize applicant volume
- Balanced objective – optimize equally for speed, quantity, and cost.
- Target a specific number of applies. For example, 10 applies for each job in the campaign.
- Target a specific number of interviews. For example, 10 scheduled interviews for each job in the campaign.
2022-05-11
#- All campaigns created by Sponsored Jobs API are required to have an objective. If objectives are not provided by the employers at the time of new campaign creation, Sponsored Jobs API would select the appropriate objective for the campaign.
2022-08-26
#- Sponsoring jobs on TMN is now supported by Sponsored Jobs API