GraphQL schema change logs

Every change to Indeed's GraphQL schema, grouped by product and change type.

 

GraphQL schema change logs list every change to Indeed's public GraphQL schema, one log for each update to the GraphQL API reference. For what changed in each product, including documentation, see the release notes.

Each log now groups its changes by product and change type, and links each change to its page in the API reference. To learn how to read a log, see How to read change logs.

October 20, 2026

• Job Update API:
  Breaking change
  1
• Retrieve Candidates API:
  New
  37

---

October 19, 2026

• Job Sync API:
  Documentation
  1

---

October 12, 2026

• Job Sync API:
  New
  5

---

October 5, 2026

• Job Sync API:
  Documentation
  1
• Job Update API:
  Documentation
  1
• Common:
  Documentation
  1

---

Previous change logs

• 2026 change logs
• 2025 change logs
• 2024 change logs

How to read change logs

1. Products. A log has a section for each product whose part of the schema changed, such as Job Sync API. Changes to types that several APIs share are under Common.
2. Change types. Within 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, in the order of the table in Change types.
3. Reference links. Each change links to the type, query, or mutation it affects in the API reference. Removed items have no link, because their pages no longer exist.
4. Description changes. A changed description 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 in the schema	What to do
Breaking change	A type, field, argument, or enum value was removed or renamed, a type changed, or an argument or input field became required.	Check whether your queries or mutations use what changed, and update them.
Deprecation	A field or enum value is marked @deprecated, or an API is being retired.	Move to the replacement named in the deprecation reason before the item is removed.
New	A type, field, query, mutation, enum value, or optional argument was added.	Use it if it helps your integration.
Improvement	A change that makes the schema easier to rely on, such as a field that can no longer be null.	No action needed.
Policy change	A description now states a new rule or limit for using a field.	Check that your integration follows the rule.
Documentation	Only a description changed, with no change to the schema itself.	No action needed. Reread the descriptions you rely on.

 

Was this page helpful?