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.
November 16, 2026
#- Job Sync API: 1New3Documentation
November 15, 2026
#SUIDs
#Breaking change(1)
Breaking change
- Updated the search attributes SUID reference table. The changes are also in the SUID change log.
- ✏️ Updated five search attributes in the search attributes reference. Each previous attribute was deprecated and succeeded by a new attribute with a new SUID, so send the updated SUIDs instead.
| Top-level category (ja-JP) | Previous attribute (en) | Previous SUID | Updated attribute (en) | Updated SUID |
|---|---|---|---|---|
| ソフトウェアプログラム | Informatica | UM4V9 | Informatica Intelligent Data Management Cloud | YW54G |
| 運搬スキル | Picking | UKQMQ | Order picking | VWY3V |
| データ分析・可視化スキル | VLOOKUP function | 4J4NJ | VLOOKUP function | 2VV4C |
| 営業・販売スキル | Consulting sales | 2RK2A | Consultative selling | XRHB4 |
| 就業場所 | Fitness gym | BT3KA | Gym | PZUCZ |
- ❌ Removed the Online shop search attribute from the search attributes reference. It was deprecated with no successor.
| Top-level category (ja-JP) | Attribute (ja-JP) | Attribute (en) | SUID |
|---|---|---|---|
| 就業場所 | ネットショップ | Online shop | KNX7D |
Indeed Apply
#Policy change(1)
Policy change
- Added a requirement to analytics object fields and the ATS guidelines: ATS partners must show the
nameandenumKeyof every source incompleteApplicationSourceAttributionin the application list, the application view, and reports.
Documentation(2)
Documentation
- Fixed the mutation example in Apply with Indeed. It now uses
createApplyUrlForEmployerswith the correct input paths and response. - Noted in the Indeed Apply configuration reference that
indeed-apply-namedefaults tofullname.
Job Sync API
#Documentation(4)
Documentation
- Fixed the
metadatatable in Create job posting to show thatcontactPhoneis optional, and that both contact fields go incontacts.contactInfo. - Noted in Commission-based salaries (Japan) that commission-only postings omit
body.salary, and that postings with a fixed salary plus commission send the base salary. Updated the required fields table in Posting guidelines and examples (Japan) to match. - Noted in Troubleshoot Job Sync API errors that unescaped quotes or backslashes in string values often cause
GRAPHQL_PARSE_FAILED. - Noted in Troubleshoot Job Sync API errors that each seat in a request needs a unique pair of
sourceNameandseatPostingId.
Schema changes:
- November 9 log: 1New3Documentation
- November 2 log: 2Documentation
Job Sync XML
#Documentation(1)
Documentation
- Added a Job Sync XML landing page, and a Job Sync XML release notes page that collects XML feed changes from earlier releases.
Job Update API
#Schema changes:
- November 2 log: 2Documentation
ATS JavaScript Plugin
#Documentation(1)
Documentation
- Fixed the function name to
unmountButtonin Toggle visibility.
Real-Time API
#Documentation(3)
Documentation
- Fixed the authentication error code to
401in Indeed Real-time API get started. - Fixed the
connection-metadataevent name in Indeed Real-time API events. - Added
new-messageto the event types in Subscribe to server-sent events.
Employer Data API
#Documentation(3)
Documentation
- Added
sectorSUIDsandtaxIdto the Japan employer posting examples. - Added
taxId, the corporate number of aJURIDICAL_PERSONemployer, to the required fields table. - Fixed the
patchEmployerexample in Company sectors, and noted thatsectorSUIDstakes up to three SUIDs.
Hiring Lab API
#Documentation(2)
Documentation
- Added the 15,000-result maximum page size to Paginate results, and noted that the coverage queries and
allHiringLabDatasetsPublicdon't takefirstorafter. - Noted in Add a Referer header that only requests from public IP addresses need the header.
Schema changes:
- November 2 log: 10Improvement
Get started
#Documentation(2)
Documentation
- Noted in Create example employer and Create example job that Indeed gives Indeed PLUS partners their
employerIdType. - Fixed the GraphQL request in Create job posting.
Integration basics
#Documentation(4)
Documentation
- Fixed the rate limit header name to
X-RateLimit-Resetin the Webhooks integration guide. - Noted in Process events asynchronously that you must store each event durably before you return a
2xx. - Noted in the Webhooks integration guide that every step is required unless marked optional, including signature verification, and that production endpoints must use TLS 1.2 or 1.3.
- Noted in Troubleshoot GraphQL errors that an error response might have no
extensionsand only partialdata.
October 31, 2026
#Job Update API
#Breaking change(1)
Breaking change
- Removed input field
communicationInterfaceNamefrom input object typeJobPostStatusCommunicationSettingsInput. See the October 20 log.
Documentation(4)
Documentation
- Removed
communicationInterfaceNamefrom the request examples and from thestatusCommunicationdescription inJobPostSurfaceStatus, because every agency account now has a default. If a job returnsisRejected: truewith no messages, retry withcommunicationLocale: "en". If that doesn't work, contact your Indeed representative. - Added a beta notice to the Delayed publishing guide and the rejected jobs section.
- Updated the rejected jobs steps to find all jobs where
isRejectedistrue, including sponsored jobs. - Clarified in Update job posting that an update must include only the fields that you change. A location update replaces the entire location. A salary update clears any minimum or maximum that it leaves out.
Schema changes:
- October 20 log: 1Breaking change
Retrieve Candidates API
#Schema changes:
- October 20 log: 1New
Job Sync API
#Documentation(2)
Documentation
- Removed the step about the retired simulated GraphQL environment from the Job Sync API integration guide.
- Updated Location information (Japan) to allow an address for
"Fully Remote"jobs. The postal code and building name are now described as optional but recommended.
Schema changes:
- October 19 log: 1Documentation
Job Sync XML
#Documentation(2)
Documentation
- Clarified that the
<company>element in the XML feed reference is the company or brand name that job seekers see on Indeed. Added guidance for subsidiaries and franchises, and fixed the example. - Fixed the
<remotetype>link in the XML feed reference. It now points to the whole "How to post a remote job on Indeed" article, because the sections it linked to no longer exist.
Publisher JavaScript Plugin
#Documentation(1)
Documentation
- Corrected the attribute table in Publisher JavaScript Plugin to show that
data-indeed-search-occupationsis optional.
Send Candidates API
#Documentation(3)
Documentation
- Corrected the attachment size limits in Best practices. Each file can be up to 6 MB, and all attachments together up to 15 MB. Added how to advance a polling cursor without skipping updates.
- Clarified in Data types and file handling which attachment types Indeed keeps and how to diagnose failed file uploads.
- Added Japanese translations of Best practices and Data types and file handling.
Employer Registration API
#Documentation(2)
Documentation
- Corrected the response types for
manageFeaturesForEmployerandfindRegisteredEmployersin the Employer Registration API guide. Added instructions for paging through registrations. - Added a Japanese translation of the Employer Registration API guide.
Disposition Sync API
#Documentation(2)
Documentation
- Added a check to Validate your content in Requirements for Japan partners. Each test call must now return an empty
failedDispositionsand no errors. - Clarified in Indeed standard disposition statuses that the
DROPPED_*statuses describe delivery failures, not candidate statuses. Added a link to the status table for partners in Japan.
Indeed Apply
#Documentation(3)
Documentation
- Restructured Apply with Indeed around two integration options: the Apply with Indeed JavaScript and the
applyUrlForEmployersmutation. - Clarified in Specify parameters that
data-indeed-apply-encryptedFeedUrltakes the XML feed URL. - Clarified in Apply with Indeed and Troubleshoot errors when to retry a failed apply URL request. Retry only on
INTERNAL_SERVER_ERROR, with exponential backoff. OnGRAPHQL_PARSE_FAILEDorBAD_USER_INPUT, fix the request before you resend it.
Employer Data API
#Documentation(1)
Documentation
- Updated the
patchEmployerexamples in the Employer Data API guide to requestattributeUpdatedinstead of the deprecatedresponseCodefield.
Integration basics
#Documentation(3)
Documentation
- Rewrote GraphQL at Indeed as a starting page. It explains the endpoint and schema, the access you need, and where to go next.
- Restructured the Webhooks integration guide into numbered integration steps. Delivery monitoring is now a required step. Added how to handle duplicate and out-of-order events.
- Fixed the variables example in Best practices for GraphQL clients to be a valid
QuestionAnswersInput. Rewrote the error code guidance for partners who call Indeed APIs.
Authentication
#Documentation(4)
Documentation
- Fixed the
Content-Typefor token requests in the OAuth reference and the grant type guides. It's nowapplication/x-www-form-urlencoded. - Updated Token exchange grant type (OAuth) to send the token request with an
Authorization: Basicheader. - Clarified in the OAuth reference which parameters each grant type uses. The 3-legged code exchange doesn't use
scope, and token exchange needsopenidonly in some cases. - Updated the Log in with Indeed example to request only the
emailscope.
Docs site
#Documentation(2)
Documentation
- Improved search on docs.indeed.com so it returns the page you're most likely looking for first. For example, searching for "job sync api" or "indeed apply" now returns the Job Sync API or Indeed Apply landing page.
- Improved accessibility across the site for keyboard and screen reader users, including image descriptions on the ATS JavaScript Plugin page, headings and navigation labels on API guides, table headers in Indeed standard disposition statuses, and an image zoom dialog that keeps focus until you close it.
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.