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.

October 31, 2026

Job Update API

Breaking change

(1)

• Removed input field communicationInterfaceName from input object type JobPostStatusCommunicationSettingsInput. See the October 20 log.

Documentation

(4)

• Removed communicationInterfaceName from the request examples and from the statusCommunication description in JobPostSurfaceStatus, because every agency account now has a default. If a job returns isRejected: true with no messages, retry with communicationLocale: "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 isRejected is true, 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:
  Breaking change
  1

Job Sync API

Documentation

(2)

• 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:
  Documentation
  1

Job Sync XML

Documentation

(2)

• 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)

• Corrected the attribute table in Publisher JavaScript Plugin to show that data-indeed-search-occupations is optional.

Send Candidates API

Documentation

(3)

• 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)

• Corrected the response types for manageFeaturesForEmployer and findRegisteredEmployers in 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)

• Added a check to Validate your content in Requirements for Japan partners. Each test call must now return an empty failedDispositions and 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)

• Restructured Apply with Indeed around two integration options: the Apply with Indeed JavaScript and the applyUrlForEmployers mutation.
• Clarified in Specify parameters that data-indeed-apply-encryptedFeedUrl takes 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. On GRAPHQL_PARSE_FAILED or BAD_USER_INPUT, fix the request before you resend it.

Employer Data API

Documentation

(1)

• Updated the patchEmployer examples in the Employer Data API guide to request attributeUpdated instead of the deprecated responseCode field.

Integration basics

Documentation

(3)

• 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)

• Fixed the Content-Type for token requests in the OAuth reference and the grant type guides. It's now application/x-www-form-urlencoded.
• Updated Token exchange grant type (OAuth) to send the token request with an Authorization: Basic header.
• Clarified in the OAuth reference which parameters each grant type uses. The 3-legged code exchange doesn't use scope, and token exchange needs openid only in some cases.
• Updated the Log in with Indeed example to request only the email scope.

Docs site

Documentation

(2)

• 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.

Retrieve Candidates API

Schema changes:

• October 26 log:
  Documentation
  1
• October 20 log:
  New
  37

---

October 15, 2026

Job Update API

New

(2)

• 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 status input that rejection messages require, since messagingTagMatches returns empty without it.

Documentation

(1)

• Clarified on JobPostStatus that a HIDDEN global status overrides a higher per-surface status such as ORGANIC.

Schema changes:

• October 5 log:
  Documentation
  1

Job Sync API

Documentation

(1)

• 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_ERROR with HTTP status 429.

Schema changes:

• October 12 log:
  New
  5
• October 5 log:
  Documentation
  1

Publisher JavaScript Plugin

Documentation

(1)

• Added two limits on the data-indeed-search-where attribute to Enable job search. It takes exactly one work location and accepts no geography finer than a municipality.

Candidate Sync APIs

Documentation

(3)

• Added the sendApplications requirement 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 fetchAssets response.

Disposition Sync API

Documentation

(1)

• 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)

• Added a deprecation notice for version 0.0 of the screener question schema to the Questions schema section. Support ended December 8, 2025, and integrations still on 0.0 send 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 smartFitScore in the analytics object fields table, since Indeed includes the field whenever the employer has enrolled in Smart Screening.

SCIM API

Documentation

(2)

• 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
  Documentation
  1

---

Previous release notes

• 2026 release notes
• 2025 release notes
• 2024 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 types and what to do

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

• Job Sync API
• Job Sync XML
• Job Update API
• ATS JavaScript Plugin
• Publisher JavaScript Plugin

Candidates

• Candidate Sync APIs:
  • Retrieve Candidates API
  • Send Candidates API
  • Employer Registration API
• Disposition Sync API
• Indeed Apply
• Real-Time API

Employers

• Employer Data API
• SCIM API

Labor market data

• Hiring Lab API

Platform and support

• Get started
• Integration basics
• Authentication
• Support

GraphQL schema change logs

Every change to the GraphQL schema, grouped by product and change type, is in the GraphQL schema change logs.

 

Was this page helpful?