Release notes
Stay up to date with Indeed product features, changes, and bug fixes.Find out what changed in Indeed's partner APIs, tools, and documentation, how it affects your integration, and what to do about it. Changes are grouped by product and change type. See How to read release notes.
Schema changes since the last release
#These GraphQL schema changes are live. The next release notes will summarize them.
October 20, 2026
#- Job Update API: 1Breaking change
- Retrieve Candidates API: 37New
October 19, 2026
#- Job Sync API: 1Documentation
October 15, 2026
#Job Update API
#New(2)
New
- Published a Delayed publishing guide in English and Japanese for agencies that review a client's job before job seekers see it. It covers enabling the hold in Partner Console, reviewing the held job, publishing it with
publishSourcedJobPostings, and the fact that each new update from the client's ATS holds the job again. - Updated the rejected jobs examples with the
statusinput that rejection messages require, sincemessagingTagMatchesreturns empty without it.
Documentation(1)
Documentation
- Clarified on
JobPostStatusthat aHIDDENglobal status overrides a higher per-surface status such asORGANIC.
Schema changes:
- October 5 log: 1Documentation
Job Sync API
#Documentation(1)
Documentation
- Fixed the rate limits section in English and Japanese to show that expirations count toward the same per-request-size limits as job creation, and that a throttled call returns
SUBREQUEST_HTTP_ERRORwith HTTP status429.
Schema changes:
- October 12 log: 5New
- October 5 log: 1Documentation
Publisher JavaScript Plugin
#Documentation(1)
Documentation
- Added two limits on the
data-indeed-search-whereattribute to Enable job search. It takes exactly one work location and accepts no geography finer than a municipality.
Candidate Sync APIs
#Documentation(3)
Documentation
- Added the
sendApplicationsrequirement to Initialize application and upload attachments in the Send Candidates API guide. The feature must be enabled on the employer registration first. - Moved application deletion out of the Send Candidates sync workflow, where Delete application is now a separate operation rather than a routine step.
- Updated Asset types in the Retrieve Candidates API guide to show which identifier belongs to which asset type in a mixed
fetchAssetsresponse.
Disposition Sync API
#Documentation(1)
Documentation
- Clarified in the Disposition Sync API integration guide that one OAuth client ID covers both the Review phase and the Production phase, with no separate app for testing.
Indeed Apply
#Documentation(3)
Documentation
- Added a deprecation notice for version
0.0of the screener question schema to the Questions schema section. Support ended December 8, 2025, and integrations still on0.0send job seekers to the employer's website. - Added the 1 MB size limit for the questions file to the JSON for screener questions reference.
- Removed the "Optional" label from
smartFitScorein the analytics object fields table, since Indeed includes the field whenever the employer has enrolled in Smart Screening.
SCIM API
#Documentation(2)
Documentation
- Updated Update user by ID in the SCIM API guide with the full endpoint URL rather than a relative path.
- Clarified in the SCIM API guide that SCIM end users do not have a consumer Indeed.com account and cannot sign in to Indeed directly.
GraphQL schema changes
#- Other schema changes — Common: October 5 log 1Documentation
September 30, 2026
#Job Update API
#New(1)
New
- Added a rejected jobs section to the Job Update API guide. Request
statusCommunicationonsurfaceStatusesin afindEmployerJobsPartnercall to see why a job was rejected, then fix the issue and resubmit.
Documentation(2)
Documentation
- Clarified in the seat management guide that each seat must be a real work location, not a way to advertise in markets where the job is not based.
- Fixed the
clearSeatsdescription in the same guide: it expires agency-created seats, but only removes updates from ATS-created seats.
Schema changes:
- September 21 log: 3New13Documentation
Job Sync API
#Documentation(2)
Documentation
- Clarified on
SourcedJobPostingMetadataInputandSourcedJobPostingPhotoInputthat job photos are supported only for jobs in Japan. Sending these fields elsewhere has no effect. - Added a note to the XML feed reference that the
hide_from_indeed_searchelement is not available in Japan.
Schema changes:
- September 28 log: 1Policy change1Documentation
- September 21 log: 2Documentation
Indeed Apply
#Documentation(1)
Documentation
- Clarified in the Indeed Apply configuration reference that
indeed-apply-resumefieldsrequiredrequests resume fields but does not guarantee them. A job seeker with no prior experience can skip a required page, and the application data omits those fields.
Get started
#Documentation(1)
Documentation
- Updated the Japanese Indeed Documentation (Indeed ドキュメント), Get started (はじめに), Integration basics (連携の基本), Indeed PLUS, and API guides (APIガイド) landing pages with consistent terminology.
Integration basics
#Documentation(1)
Documentation
- Updated the language codes, country codes, and locales table to 103 locales, adding Hungary, Austria, and Brazil. The table is now linked from Integration basics and the API reference.
Docs site
#Documentation(4)
Documentation
- Reorganized the release notes to group each product's changes by change type, such as Breaking change, New, and Documentation, so changes that need action stand out. To learn what each type means, see Change types.
- Added a summary of each product's GraphQL schema changes to its release notes section, linked to that product's section of the GraphQL schema change logs. The change logs are also grouped by product and change type.
- Combined each year's release notes into one page, such as the 2026 release notes, with each release under its date, newest first. Links to each release's former page still work.
- Published a release notes page for every product, with all of its changes, newest first. Find them in Release notes by product.
Candidate Sync APIs
#Schema changes:
- September 21 log: 4Documentation
Retrieve Candidates API
#Schema changes:
- September 21 log: 69Documentation
Send Candidates API
#Schema changes:
- September 21 log: 49Documentation
Employer Registration API
#Schema changes:
- September 21 log: 61Documentation
Previous release notes
#How to read release notes
#Each release is a section headed by its publication date. Inside a release:
- Products — Each product or documentation area that changed has its own heading, such as Job Sync API or Get started. Products with the most urgent change types come first.
- Change types — Under each product, changes are grouped by change type. Each group starts with a tag that names the type and shows how many changes it holds. Groups always appear in the order of the Change types table, starting with Breaking change and Deprecation, the changes most likely to need action.
- Schema changes — If a product's GraphQL schema changed during the release, its section ends with a Schema changes list. Each item links to the product's section of a schema change log and shows a change type tag and count for each type of change. Schema breaking changes and deprecations are also listed as their own entries in the matching group, so they stand out.
- GraphQL schema changes — The last section of a release lists schema changes that belong to no product section, such as changes shared across APIs.
In the schema change logs, a description change shows the old and new text as a compact diff: removed words are struck through, and added words are highlighted.
Change types
#| Change type | What it means | What to do |
|---|---|---|
Breaking change | Change that can break an existing integration, such as a removed field, changed type, or new required input. | Check whether your integration uses what changed, and update it. |
Deprecation | Advance notice that a feature or field will be removed, with time to migrate. | Plan your migration before the removal date. |
New | New capability, such as a new API, query, mutation, field, or webhook. | Adopt it if it helps your integration. |
Bug fix | Correction to product behavior that didn't work as intended. | Remove any workaround you added for the issue. |
Improvement | Better performance or capacity, such as lower latency or a higher limit. | No action needed. |
Policy change | Change to the rules for using a product, such as usage policies, quotas, or content requirements, with no change to the API itself. | Review the policy and change how you use the product if needed. |
Security change | Change to authentication, credential handling, token expiration, or encryption. | Review your security setup and update it as described. |
Documentation | Change to the documentation only, such as a clarification, new example, correction, or translation, with no change to the product. | No action needed. Reread the changed sections you rely on. |
Release notes by product
#Job postings
#Candidates
#Employers
#Labor market data
#Platform and support
#GraphQL schema change logs
#Every change to the GraphQL schema, grouped by product and change type, is in the GraphQL schema change logs.