2026-08-24

GraphQL schema change log: 2026-08-24

📘 Documentation: Updated the GraphQL schema and the GraphQL API Reference with these changes:

[log] ⚠ Input field jobRequisitionId of type [String!] was added to input object type FindEmployerJobsPartnerFilterInput
[log] ✔ Description:
```
Seat body for adding a seat.
```
On type AddSeatBodyInput has changed to:
```
Body data for a new seat.
```
[log] ✔ Input field AddSeatBodyInput.location description changed from:
```
Location for the seat.
```
To:
```
Seat location.
```
[log] ✔ Input field AddSeatBodyInput.salary description changed from:
```
Salary for the seat.
```
To:
```
Seat salary.
```
[log] ✔ Description:
```
One seat add operation.
```
On type AddSeatInput has changed to:
```
One seat to add.
```
[log] ✔ Input field AddSeatInput.body description changed from:
```
Seat body data.
```
To:
```
Seat body.
```

[log] ✔ Input field AddSeatInput.seatPostingId description changed from:

Agency-provided identifier for the seat. Must be unique across all seats on the job. Use it in later `updateSeats` and `clearSeats` requests.

To:

Agency-provided seat ID. Must be unique across all seats on the job.

[log] ✔ Description:
```
Seat metadata for adding a seat.
```
On type AddSeatMetadataInput has changed to:
```
Metadata for a new seat.
```
[log] ✔ Input field AddSeatMetadataInput.taxonomyClassification description changed from:
```
Taxonomy classification for the seat.
```
To:
```
Taxonomy classification.
```
[log] ✔ Input field AddSeatMetadataInput.trackingUrl description changed from:
```
Tracking URL for the seat.
```
To:
```
Tracking URL.
```
[log] ✔ Input field AddSeatMetadataInput.url description changed from:
```
Job URL for the seat.
```
To:
```
Job URL.
```
[log] ✔ Description:
```
Result for one seat add operation.
```
On type AddSeatResult has changed to:
```
Result for one seat add.
```
[log] ✔ Field AddSeatResult.employerJobId description changed from:
```
Base64-encoded IRI of the employer job.
```
To:
```
Employer job ID as a base64-encoded IRI.
```

[log] ✔ Field AddSeatResult.jobKey description changed from:

Encrypted `aggJobId` for the seat. Pass it to `SeatIdentifierInput.jobKey` in `updateSeats` or `clearSeats`.
`null` if the seat add failed.

To:

Encrypted `aggJobId` for the seat returned by [`addSeats`](/api/job/mutations/jobsIngest/addSeats).
Pass it to `SeatIdentifierInput.jobKey` in [`updateSeats`](/api/job/mutations/jobsIngest/updateSeats) or [`clearSeats`](/api/job/mutations/jobsIngest/clearSeats).
If the seat add failed, the value is null.

[log] ✔ Field AddSeatResult.seatPostingId description changed from:
```
Agency-provided seat identifier.
```
To:
```
Agency-provided seat ID.
```
[log] ✔ Field AddSeatResult.sourcedPostingId description changed from:
```
UUID form of the employer job ID.
```
To:
```
Employer job ID as a UUID.
```
[log] ✔ Description:
```
`addSeats` input.
```
On type AddSeatsInput has changed to:
```
Input for `addSeats`.
```
[log] ✔ Description:
```
`addSeats` return type.
```
On type AddSeatsPayload has changed to:
```
Payload for `addSeats`.
```
[log] ✔ Description:
```
One seat clear operation.
```
On type ClearSeatInput has changed to:
```
One seat to remove.
```
[log] ✔ Input field ClearSeatInput.seatIdentifier description changed from:
```
Seat to remove. Provide one field.
```
To:
```
Seat to remove. Provide one field.
```
[log] ✔ Description:
```
Result for one seat clear operation.
```
On type ClearSeatResult has changed to:
```
Result for one seat clear.
```
[log] ✔ Field ClearSeatResult.employerJobId description changed from:
```
Base64-encoded IRI of the employer job.
```
To:
```
Employer job ID as a base64-encoded IRI.
```

[log] ✔ Field ClearSeatResult.jobKey description changed from:

Encrypted `aggJobId` for the seat.

To:

Encrypted `aggJobId` for the seat returned by [`addSeats`](/api/job/mutations/jobsIngest/addSeats).
Pass it to `SeatIdentifierInput.jobKey` in [`updateSeats`](/api/job/mutations/jobsIngest/updateSeats) or [`clearSeats`](/api/job/mutations/jobsIngest/clearSeats).
If the seat add failed, the value is null.

[log] ✔ Field ClearSeatResult.seatPostingId description changed from:
```
Agency-provided seat identifier.
```
To:
```
Agency-provided seat ID.
```
[log] ✔ Field ClearSeatResult.sourcedPostingId description changed from:
```
UUID form of the employer job ID.
```
To:
```
Employer job ID as a UUID.
```
[log] ✔ Description:
```
`clearSeats` input.
```
On type ClearSeatsInput has changed to:
```
Input for `clearSeats`.
```
[log] ✔ Input field ClearSeatsInput.seatRemovals description changed from:
```
Seat removals to process. Accepts one item.
```
To:
```
Seat removals to process. Accepts one item.
```
[log] ✔ Description:
```
`clearSeats` return type.
```
On type ClearSeatsPayload has changed to:
```
Payload for `clearSeats`.
```

[log] ✔ Description:

Clears updates from `updateSourcedJobPostings`.
Not atomic. Errors can partially clear updates.

On type ClearSourcedJobPostingUpdateInput has changed to:

One job posting with updates from `updateSourcedJobPostings` to clear. Not atomic. Errors can partially clear updates.

[log] ✔ Input field ClearSourcedJobPostingUpdateInput.sourcedPostingId description changed from:

Job post UUID from `createSourcedJobPostings`, or employer job ID as a UUID or base64-encoded [`EmployerJob`](/api/job/objects/EmployerJob) [IRI](/getstarted/iris).

To:

Job post UUID from `createSourcedJobPostings`. Also accepts an employer job ID as a UUID or a base64-encoded [`EmployerJob`](/api/job/objects/EmployerJob) [IRI](/integration-basics/graphql-at-indeed/iris).

[log] ✔ Description:
```
Return type for each `clearJobPostingUpdates` result.
```
On type ClearSourcedJobPostingUpdateResult has changed to:
```
Result for one `clearSourcedJobPostingUpdates` operation.
```
[log] ✔ Field ClearSourcedJobPostingUpdateResult.jobPosting description changed from:
```
The cleared job posting, or null if nothing was cleared.
```
To:
```
Cleared job posting. If nothing was cleared, null.
```
[log] ✔ Description:
```
`clearSourcedJobPostingUpdates` input.
```
On type ClearSourcedJobPostingUpdatesInput has changed to:
```
Input for `clearSourcedJobPostingUpdates`.
```
[log] ✔ Description:
```
Return type for `clearSourcedJobPostingUpdates`.
```
On type ClearSourcedJobPostingUpdatesPayload has changed to:
```
Payload for `clearSourcedJobPostingUpdates`.
```

[log] ✔ Field ClearSourcedJobPostingUpdatesPayload.results description changed from:

Results for each clear operation.
Array items are never null, but `jobPosting` can be null if nothing was cleared.

To:

Results for each clear. Array items are never null.
If nothing was cleared, `jobPosting` can be null.

[log] ✔ Input field ConditionConstraintInput.values description changed from:
```
Values that satisfy the condition when the id question matches.
```
To:
```
Values that satisfy the condition when that question matches.
```

[log] ✔ Description:

Intermediary type. A null `jobPosting` indicates a creation error. The GraphQL `errors` object shows the problem by index.

On type CreateSourcedJobPostingResult has changed to:

Intermediary type. If a creation error occurs, `jobPosting` is null.
The GraphQL `errors` array shows the problem by index.

[log] ✔ Field CreateSourcedJobPostingsPayload.results description changed from:

Return type for each job posting in `createSourcedJobPostings`. Array values cannot be null, but `jobPosting` can be null if rejected. See the `errors` object for details.

To:

Result for each job posting in `createSourcedJobPostings`.
Array entries cannot be null. If Indeed rejects the job, `jobPosting` can be null.
See the GraphQL `errors` array for details.

[log] ✔ Input field DateQuestionInput.condition description changed from:

Conditional question. Depends on a previous answer. Specify the previous question ID and activating option value.
Example: if applicant answers yes to military service, show a follow-up question about branch of service.

To:

Show this question only when a previous answer matches. Set the previous question ID and the value that activates this question.
**Example**: If the applicant answers yes to military service, show a follow-up about branch of service.

[log] ✔ Input field DateQuestionInput.format description changed from:

Requires `dd/MM/yyyy` format or Unicode CLDR locale-specific format. Uses `SimpleDateFormat`.
Use `MM` for month (`mm` causes errors).
Format affects ATS data transfer and min/max parsing. Job seekers enter dates in their locale format.
Use `yyyy` for year (`yy` causes confusion).

To:

Use `dd/MM/yyyy` or a Unicode CLDR locale format. Indeed uses `SimpleDateFormat`.
Use `MM` for month (`mm` causes errors). Use `yyyy` for year (`yy` can confuse job seekers).
The format affects ATS data transfer and min/max parsing. Job seekers enter dates in their locale format.

[log] ✔ Input field DateQuestionInput.required description changed from:

`true`: question is required. Unanswered optional questions return `"` (empty string). Default: `false`.

To:

If `true`, the question is required. Unanswered optional questions return `"`. Default: `false`.

[log] ✔ Input field DateQuestionQualificationInput.range description changed from:

Evaluation method: `range`. Answers must fall within the defined min/max values.

To:

Range evaluation. The answer must fall between the min and max values.

[log] ✔ Input field DateQuestionQualificationInput.type description changed from:
```
Qualification type affecting the application in Indeed Apply.
```
To:
```
How the qualification affects the Indeed Apply application.
```

[log] ✔ Input field DateScreenerQuestionInput.qualification description changed from:

Qualification criterion for job requirements. Applicants must meet employer-defined conditions.
Non-blocking: all applications delivered regardless of meeting criteria.

To:

Qualification for this question. Indeed still delivers applications that do not meet the criterion (`NON_BLOCKING`).

[log] ✔ Description:
```
Date with time (isoformat)
```
On type DateTime has changed to:
```
Datetime as [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339).
```

[log] ✔ Input field DecimalTextQuestionInput.condition description changed from:

Conditional question. Depends on a previous answer. Specify the previous question ID and activating option value.
Example: if applicant answers yes to military service, show a follow-up question about branch of service.

To:

Show this question only when a previous answer matches. Set the previous question ID and the value that activates this question.
**Example**: If the applicant answers yes to military service, show a follow-up about branch of service.

[log] ✔ Input field DecimalTextQuestionInput.required description changed from:

`true`: question is required. Unanswered optional questions return `"` (empty string). Default: `false`.

To:

If `true`, the question is required. Unanswered optional questions return `"`. Default: `false`.

[log] ✔ Input field DecimalTextScreenerQuestionInput.qualification description changed from:

Qualification criterion for job requirements. Applicants must meet employer-defined conditions.
Non-blocking: all applications delivered regardless of meeting criteria.

To:

Qualification for this question. Indeed still delivers applications that do not meet the criterion (`NON_BLOCKING`).

[log] ✔ Description:

Questions about the applicants protected class (ethnicity, gender, disability). Some jurisdictions regulate these questions, requiring special handling by Indeed and your systems.
Demographic questions are limited to U.S.-based jobs for EEO compliance.
Do not mix general screener questions here. Place work experience, skills, or certification questions in [`ScreenerQuestionBodyInput`](/api/job/objects/ScreenerQuestionBodyInput).`screenerQuestions` field.

On type DemographicQuestionsBodyInput has changed to:

Questions about a protected class, such as ethnicity, gender, or disability.
Some jurisdictions regulate these questions. Indeed and your systems must handle them separately.
Limited to U.S. jobs for EEO compliance.
Do not include general screener questions here.
Put work experience, skills, or certification questions in [`screenerQuestions`](/api/job/objects/ScreenerQuestionBodyInput).

[log] ✔ Input field DemographicQuestionsBodyInput.date description changed from:

Date question. Displays as date text field.
Requires `dd/MM/yyyy` format or Unicode CLDR locale-specific format. Uses `SimpleDateFormat`.
Use `MM` for month (`mm` causes errors). Use `yyyy` for year (`yy` causes confusion).
Format affects ATS data transfer and min/max parsing. Job seekers enter dates in their locale format.

To:

Date question. Shows a date field.
Use `dd/MM/yyyy` or a Unicode CLDR locale format. Indeed uses `SimpleDateFormat`.
Use `MM` for month (`mm` causes errors). Use `yyyy` for year (`yy` can confuse job seekers).
The format affects ATS data transfer and min/max parsing. Job seekers enter dates in their locale format.

[log] ✔ Input field DemographicQuestionsBodyInput.information description changed from:

Display-only text for explanations or section headings. No response required.
See [information](https://docs.indeed.com/indeed-apply/screener-questions#information).

To:

Display-only text for explanations or section headings. Job seekers do not answer.
See [information](https://docs.indeed.com/indeed-apply/screener-questions#information).

[log] ✔ Input field DemographicQuestionsBodyInput.multiselect description changed from:
```
Multiple-answer question. Displays as checkboxes.
```
To:
```
Multiple-answer question. Shows checkboxes.
```

[log] ✔ Input field DemographicQuestionsBodyInput.pageBreak description changed from:

Groups questions on a page. Questions between pagebreaks appear together.
Maximum: 20 questions per page.
Default: 3 per page (desktop), all on one page (mobile).

To:

Groups questions on a page. Questions between page breaks appear together.
Maximum: 20 questions per page.
Default: 3 per page on desktop, all on one page on mobile.

[log] ✔ Input field DemographicQuestionsBodyInput.select description changed from:

Multiple-choice question. Single answer only.
1-5 answers: radio buttons. 6+ answers: dropdown list.

To:

Multiple-choice question. Job seekers select one answer.
1–5 options: radio buttons. 6 or more: dropdown.

[log] ✔ Input field DemographicQuestionsBodyInput.text description changed from:

Short-answer question. Displays as single-line text field.
Formats: `integer`, `decimal`, `numeric_text`. See [JSON questions parameters](https://docs.indeed.com/indeed-apply/screener-questions#json-questions-parameters).

To:

Short answer. Shows a single-line text field.
Formats: `integer`, `decimal`, `numeric_text`.
See [JSON questions parameters](https://docs.indeed.com/indeed-apply/screener-questions#json-questions-parameters).

[log] ✔ Input field DemographicQuestionsBodyInput.textarea description changed from:
```
Long-form answer question. Displays as multi-line text field.
```
To:
```
Long-form answer. Shows a multi-line text field.
```

[log] ✔ Description:

Identifies the employer job. Provide exactly one field: `sourcedPostingId` as a UUID, or `employerJobId` as a base64-encoded IRI.

On type EmployerJobIdentifierInput has changed to:

Identifies the employer job. Provide exactly one field: `sourcedPostingId` as a UUID, or `employerJobId` as a base64-encoded IRI.

[log] ✔ Input field EmployerJobIdentifierInput.employerJobId description changed from:

Base64-encoded IRI from `EmployerJob`. Accepts values from `createSourcedJobPostings` or `EmployerJob`.

To:

Base64-encoded IRI from `EmployerJob`. Accepts values from `createSourcedJobPostings` or `EmployerJob`.

[log] ✔ Description:
```
Input containing Indeed Employer Job ID.
```
On type ExpireSourcedJobBySourcedPostingIdInput has changed to:
```
Input containing Indeed Employer job ID.
```

[log] ✔ Input field ExpireSourcedJobBySourcedPostingIdInput.sourcedPostingId description changed from:

Indeed Employer Job ID (UUID4). Generated for each job posting.
Returned in the job creation response. Use to expire the job.

To:

Indeed Employer job ID (UUID4). Generated for each job posting.
Returned in the job creation response. Use to expire the job.

[log] ✔ Field ExpireSourcedJobResult.inputData description changed from:
```
Input values for this result. Is null on error.
```
To:
```
Input values for this result. Null on error.
```
[log] ✔ Field ExpireSourcedJobsBySourcedPostingIdPayload.results description changed from:
```
Input for `expireSourcedJobsBySourcedPostingId` mutation.
```
To:
```
Expiration results.
```

[log] ✔ Input field FileQuestionInput.condition description changed from:

Conditional question. Depends on a previous answer. Specify the previous question ID and activating option value.
Example: if applicant answers yes to military service, show a follow-up question about branch of service.

To:

Show this question only when a previous answer matches. Set the previous question ID and the value that activates this question.
**Example**: If the applicant answers yes to military service, show a follow-up about branch of service.

[log] ✔ Input field FileQuestionInput.required description changed from:

`true`: question is required. Unanswered optional questions return `"` (empty string). Default: `false`.

To:

If `true`, the question is required. Unanswered optional questions return `"`. Default: `false`.

[log] ✔ Input field FreeformTextQuestionInput.condition description changed from:

Conditional question. Depends on a previous answer. Specify the previous question ID and activating option value.
Example: if applicant answers yes to military service, show a follow-up question about branch of service.

To:

Show this question only when a previous answer matches. Set the previous question ID and the value that activates this question.
**Example**: If the applicant answers yes to military service, show a follow-up about branch of service.

[log] ✔ Input field FreeformTextQuestionInput.required description changed from:

`true`: question is required. Unanswered optional questions return `"` (empty string). Default: `false`.

To:

If `true`, the question is required. Unanswered optional questions return `"`. Default: `false`.

[log] ✔ Input field FreeformTextQuestionInput.validationRuleKey description changed from:

Optional key referencing an external validation rule. Enforced on the job seekers answer at apply time. Unknown keys are rejected at ingestion.

To:

Optional key for an external validation rule. Indeed enforces it on the job seekers answer at apply time. Unknown keys fail ingestion.

[log] ✔ Description:

Input that controls whether the job posting appears in Indeed search. Reason codes:
- `CONFIDENTIAL_JOB`: Confidential job postings that should not appear in Indeed search.
Example: An employer discreetly replacing a role hides the posting from Indeed search while using targeted channels (AutoSourcer, I2A, Smart Sourcing, or off-Indeed outreach).
- `TALENT_POOL`: Jobs not currently open that build a candidate pool for future openings. These postings should not appear in Indeed search.
Example: A company planning to expand next quarter creates a talent pool posting to gather candidates before positions become available.
- `OPT_OUT`: Rare or exceptional cases where jobs are hidden from Indeed search for reasons not covered by other codes. Not for general opt-out or policy circumvention. Always discuss with your partner manager in advance.

On type HideFromIndeedSearchInput has changed to:

Input that controls whether the job posting appears in Indeed search. Reason codes:
- `CONFIDENTIAL_JOB`: Hide a confidential posting from Indeed search.
**Example**: An employer replacing a role privately hides the posting from search and uses targeted recruiting channels instead.
- `TALENT_POOL`: Hide a posting that is not currently open. Use it to build a candidate pool for future openings.
**Example**: A company planning to expand next quarter collects candidates before the roles open.
- `OPT_OUT`: Hide a posting for a rare case that the other codes do not cover. Do not use this for a general opt-out or to bypass policy. Discuss with your partner manager first.

[log] ✔ Input field HierarchicalOptionInput.condition description changed from:

Conditional question. Depends on a previous answer. Specify the previous question ID and activating option value.
Example: if applicant answers yes to military service, show a follow-up question about branch of service.

To:

Show this question only when a previous answer matches. Set the previous question ID and the value that activates this question.
**Example**: If the applicant answers yes to military service, show a follow-up about branch of service.

[log] ✔ Input field HierarchicalQuestionInput.condition description changed from:

Conditional question. Depends on a previous answer. Specify the previous question ID and activating option value.
Example: if applicant answers yes to military service, show a follow-up question about branch of service.

To:

Show this question only when a previous answer matches. Set the previous question ID and the value that activates this question.
**Example**: If the applicant answers yes to military service, show a follow-up about branch of service.

[log] ✔ Input field HierarchicalQuestionInput.hierarchicalOptions description changed from:

Displays follow-up questions based on previous answers. Example: select state, then show cities in that state.
Limited to 3 levels.

To:

Follow-up questions based on a previous answer.
**Example**: Select a state, then show cities in that state.
Limited to 3 levels.

[log] ✔ Input field HierarchicalQuestionInput.required description changed from:

`true`: question is required. Unanswered optional questions return `"` (empty string). Default: `false`.

To:

If `true`, the question is required. Unanswered optional questions return `"`. Default: `false`.

[log] ✔ Description:

Resume field requirement values. See [Indeed Resume JSON object fields](https://docs.indeed.com/indeed-apply/application-data#indeed-resume-json-object-fields).

On type IndeedApplyConfigurationResumeField has changed to:

Resume field requirement values.
See [Indeed Resume JSON object fields](https://docs.indeed.com/indeed-apply/application-data#indeed-resume-json-object-fields).

[log] ✔ Input field IndeedApplyQuestionsDetailsInput.questions description changed from:

Indeed Apply screener questionnaire definition (V1.x standard). See [documentation](https://docs.indeed.com/indeed-apply/screener-questions).

To:

Indeed Apply screener questionnaire definition (V1.x standard).
See [documentation](https://docs.indeed.com/indeed-apply/screener-questions).

[log] ✔ Input field IndeedApplyScreenerQuestionsDefinitionInput.demographicQuestions description changed from:

Demographic questions relate to protected class information (ethnicity, gender, disability).
Some jurisdictions regulate these questions. Indeed and your systems must handle them specially.
Limited to U.S. jobs for EEO compliance.
Do not include job-related questions (work experience, skills, certifications). Use `screenerQuestions` for those.

To:

Questions about a protected class, such as ethnicity, gender, or disability.
Some jurisdictions regulate these questions. Indeed and your systems must handle them separately.
Limited to U.S. jobs for EEO compliance.
Do not include job-related questions about work experience, skills, or certifications.
Put those in [`screenerQuestions`](/api/job/objects/ScreenerQuestionBodyInput).

[log] ✔ Input field IndeedApplyScreenerQuestionsDefinitionInput.screenerQuestions description changed from:

Job-related questions about experience, skills, and certifications.
Do not include demographic questions (ethnicity, gender, disability).
Some jurisdictions regulate protected class questions. Require special handling.

To:

Job-related questions about experience, skills, and certifications.
Do not include demographic questions about ethnicity, gender, or disability.
Some jurisdictions regulate protected-class questions. Handle those questions separately.

[log] ✔ Input field InformationQuestionInput.condition description changed from:

Conditional question. Depends on a previous answer. Specify the previous question ID and activating option value.
Example: if applicant answers yes to military service, show a follow-up question about branch of service.

To:

Show this question only when a previous answer matches. Set the previous question ID and the value that activates this question.
**Example**: If the applicant answers yes to military service, show a follow-up about branch of service.

[log] ✔ Input field IntegerTextQuestionInput.condition description changed from:

Conditional question. Depends on a previous answer. Specify the previous question ID and activating option value.
Example: if applicant answers yes to military service, show a follow-up question about branch of service.

To:

Show this question only when a previous answer matches. Set the previous question ID and the value that activates this question.
**Example**: If the applicant answers yes to military service, show a follow-up about branch of service.

[log] ✔ Input field IntegerTextQuestionInput.required description changed from:

`true`: question is required. Unanswered optional questions return `"` (empty string). Default: `false`.

To:

If `true`, the question is required. Unanswered optional questions return `"`. Default: `false`.

[log] ✔ Input field IntegerTextScreenerQuestionInput.qualification description changed from:

Qualification criterion for job requirements. Applicants must meet employer-defined conditions.
Non-blocking: all applications delivered regardless of meeting criteria.

To:

Qualification for this question. Indeed still delivers applications that do not meet the criterion (`NON_BLOCKING`).

[log] ✔ Object type JobsIngestMutations has description:
```
Job ingest mutations.
```
[log] ✔ Description for argument input on field JobsIngestMutations.addSeats changed from:
```
null
```
To:
```
Seat-add input.
```
[log] ✔ Field JobsIngestMutations.clearSeats description changed from:
```
Clears or expires seats from a job.
```
To:
```
Clears or expires seats on a job.
```
[log] ✔ Description for argument input on field JobsIngestMutations.clearSeats changed from:
```
null
```
To:
```
Seat-clear input.
```
[log] ✔ Description for argument input on field JobsIngestMutations.clearSourcedJobPostingUpdates changed from:
```
null
```
To:
```
Clear-updates input.
```

[log] ✔ Field JobsIngestMutations.createSourcedJobPostings description changed from:

Submits a job posting to Indeed.
Success indicates Indeed received the job. Jobs are indexed within minutes to hours after spam and fraud detection.
Rejected jobs have null `aggregationId` with an error in the GraphQL `errors` object.

To:

Submits a job posting to Indeed.
Success indicates Indeed received the job.
Jobs are indexed within minutes to hours after spam and fraud detection.
Rejected jobs have `aggregationId` set to null and an error in the GraphQL `errors` array.

[log] ✔ Description for argument input on field JobsIngestMutations.updateSeats changed from:
```
null
```
To:
```
Seat-update input.
```

[log] ✔ Field JobsIngestMutations.updateSourcedJobPostings description changed from:

Updates a sourced job. You must claim the job source before calling this mutation. Only one update is allowed per call.

To:

Updates a sourced job. Claim the job source before calling this mutation. One update per call.

[log] ✔ Description for argument input on field JobsIngestMutations.updateSourcedJobPostings changed from:
```
null
```
To:
```
Job posting update input.
```
[log] ✔ Description for enum value MatchStrategy.ALL changed from:
```
Answer must match all provided values.
```
To:
```
The answer must match all provided values.
```
[log] ✔ Description for enum value MatchStrategy.ANY changed from:
```
Answer can match any provided value.
```
To:
```
The answer can match any provided value.
```
[log] ✔ Input field MultiSelectQualificationQuestionInput.match description changed from:
```
Evaluation method: match.
```
To:
```
Match evaluation.
```
[log] ✔ Input field MultiSelectQualificationQuestionInput.type description changed from:
```
Qualification type affecting the application in Indeed Apply.
```
To:
```
How the qualification affects the Indeed Apply application.
```
[log] ✔ Input field MultifieldQuestionInput.addButtonLabel description changed from:
```
Label on the Add another button (e.g., Add Another Job).
```
To:
```
Label on the add button. For example, `Add Another Job`.
```

[log] ✔ Input field MultifieldQuestionInput.condition description changed from:

Conditional question. Depends on a previous answer. Specify the previous question ID and activating option value.

To:

Show this question only when a previous answer matches. Set the previous question ID and the value that activates this question.

[log] ✔ Input field MultifieldQuestionInput.groupLabel description changed from:
```
Label shown above each entry group (e.g., Work Experience).
```
To:
```
Label above each entry group. For example, `Work Experience`.
```

[log] ✔ Input field MultifieldQuestionInput.groupedQuestionFields description changed from:

Sub-questions repeated for each entry. Supports any `ScreenerQuestionBodyInput` variant **except** another `multifield` (rejected by validation).

To:

Sub-questions repeated for each entry. Any `ScreenerQuestionBodyInput` variant except another `multifield`. Validation rejects nested `multifield`.

[log] ✔ Input field MultifieldQuestionInput.maxEntryCount description changed from:

Maximum number of entries the jobseeker may submit. Must be >= `minEntryCount`. Defaults to 15 when omitted.

To:

Maximum number of entries the job seeker can submit. Must be greater than or equal to `minEntryCount`. Default: `15`.

[log] ✔ Input field MultifieldQuestionInput.minEntryCount description changed from:

Minimum number of entries the jobseeker must submit. 0 means optional. Defaults to 1 when omitted.

To:

Minimum number of entries the job seeker must submit. `0` means optional. Default: `1`.

[log] ✔ Description:

<!--
NOTE: the following fields should be added in the future as part of the 1.1, 1.2 and 1.3 IA update
# If set, configures the minimum amount of options that can be selected
`minSelectionCount`: Int
# If set, configures the maximum amount of options that can be selected
`maxSelectionCount`: Int
-->

On type MultiselectQuestionInput has changed to:

Multiple-answer question.

[log] ✔ Input field MultiselectQuestionInput.condition description changed from:

Conditional question. Depends on a previous answer. Specify the previous question ID and activating option value.
Example: if applicant answers yes to military service, show a follow-up question about branch of service.

To:

Show this question only when a previous answer matches. Set the previous question ID and the value that activates this question.
**Example**: If the applicant answers yes to military service, show a follow-up about branch of service.

[log] ✔ Input field MultiselectQuestionInput.required description changed from:

`true`: question is required. Unanswered optional questions return `"` (empty string). Default: `false`.

To:

If `true`, the question is required. Unanswered optional questions return `"`. Default: `false`.

[log] ✔ Input field MultiselectScreenerQuestionInput.qualification description changed from:

Qualification criterion for job requirements. Applicants must meet employer-defined conditions.
Non-blocking: all applications delivered regardless of meeting criteria.

To:

Qualification for this question. Indeed still delivers applications that do not meet the criterion (`NON_BLOCKING`).

[log] ✔ Input field NumericTextQuestionInput.condition description changed from:

Conditional question. Depends on a previous answer. Specify the previous question ID and activating option value.
Example: if applicant answers yes to military service, show a follow-up question about branch of service.

To:

Show this question only when a previous answer matches. Set the previous question ID and the value that activates this question.
**Example**: If the applicant answers yes to military service, show a follow-up about branch of service.

[log] ✔ Input field NumericTextQuestionInput.required description changed from:

`true`: question is required. Unanswered optional questions return `"`.

To:

If `true`, the question is required. Unanswered optional questions return `"`. Default: `false`.

[log] ✔ Input field NumericTextQuestionInput.validationRuleKey description changed from:

Optional key referencing an external validation rule. Enforced on the job seekers answer at apply time. Unknown keys are rejected at ingestion.

To:

Optional key for an external validation rule. Indeed enforces it on the job seekers answer at apply time. Unknown keys fail ingestion.

[log] ✔ Input field QualificationMatchAnyTextConfigurationInput.values description changed from:
```
Values applicant must match.
```
To:
```
Values the applicant must match.
```
[log] ✔ Input field QualificationMultiValueTextMatchConfigurationInput.type description changed from:
```
Whether answer must match any or all provided values.
```
To:
```
Whether the answer must match any or all provided values.
```
[log] ✔ Input field QualificationMultiValueTextMatchConfigurationInput.values description changed from:
```
Values applicant must match.
```
To:
```
Values the applicant must match.
```

[log] ✔ Description for enum value QuestionQualificationImplicationType.NON_BLOCKING changed from:

Applicant proceeds even if answer does not meet qualification. Application is delivered.

To:

The applicant can continue if the answer does not meet the qualification. Indeed still delivers the application.

[log] ✔ Description:

Questions about work experience, skills, or certifications. Do not include demographic questions (ethnicity, gender, disability) here. Some jurisdictions regulate protected class questions, requiring special handling. Place demographic questions in the [`demographicQuestions`](/api/job/objects/DemographicQuestionsBodyInput) field.

On type ScreenerQuestionBodyInput has changed to:

Questions about work experience, skills, or certifications.
Do not include demographic questions about ethnicity, gender, or disability.
Some jurisdictions regulate protected-class questions. Handle those questions separately.
Put demographic questions in [`demographicQuestions`](/api/job/objects/DemographicQuestionsBodyInput).

[log] ✔ Input field ScreenerQuestionBodyInput.date description changed from:

Date question. Displays as date text field.
Requires dd/MM/yyyy format or Unicode CLDR locale-specific format. Uses `SimpleDateFormat`.
Use `MM` for month (`mm` causes errors).
Format affects ATS data transfer and min/max parsing. Job seekers enter dates in their locale format.
Use `yyyy` for year (`yy` causes confusion).

To:

Date question. Shows a date field.
Use `dd/MM/yyyy` or a Unicode CLDR locale format. Indeed uses `SimpleDateFormat`.
Use `MM` for month (`mm` causes errors). Use `yyyy` for year (`yy` can confuse job seekers).
The format affects ATS data transfer and min/max parsing. Job seekers enter dates in their locale format.

[log] ✔ Input field ScreenerQuestionBodyInput.file description changed from:

File upload question for certifications, portfolios, or work samples. Displays as file upload field.
JSON POST response fields: `contentType`, `data`, `fileName`.
Valid file types: doc, docx, gif, jfif, jif, jpe, jpeg, jpg, pdf, png, rtf, tif, tiff, txt

To:

File upload for certifications, portfolios, or work samples.
JSON `POST` response fields: `contentType`, `data`, `fileName`.
Valid file types: `doc`, `docx`, `gif`, `jfif`, `jif`, `jpe`, `jpeg`, `jpg`, `pdf`, `png`, `rtf`, `tif`, `tiff`, `txt`

[log] ✔ Input field ScreenerQuestionBodyInput.hierarchical description changed from:

Shows follow-up questions based on previous answers. Example: select state, then show cities in that state.
Limited to 3 levels (that is, state → city → county).
Similar to conditional questions, but better when initial selection defines subsequent options.
Reduces total questions needed.

To:

Follow-up questions based on a previous answer.
**Example**: Select a state, then show cities in that state.
Limited to 3 levels (for example, state → city → county).
Similar to conditional questions. Prefer this when the first selection defines the next options. This reduces the number of questions.

[log] ✔ Input field ScreenerQuestionBodyInput.information description changed from:

Display-only text for explanations or section headings. No response required.
See [information](https://docs.indeed.com/indeed-apply/screener-questions#information).

To:

Display-only text for explanations or section headings. Job seekers do not answer.
See [information](https://docs.indeed.com/indeed-apply/screener-questions#information).

[log] ✔ Input field ScreenerQuestionBodyInput.multifield description changed from:

Multi-Field question. Groups a fixed set of sub-questions that the jobseeker can submit multiple times — e.g., enter Work Experience for each previous job.
Reduces the need for chains of conditional Do you have more to add? questions. Allowed only in screener questions. Cannot be nested (no MULTIFIELD inside a MULTIFIELDs groupedQuestionFields).

To:

Multi-field question.
Groups a fixed set of sub-questions that the job seeker can submit more than once. For example, enter work experience for each previous job.
This reduces the need for conditional “Do you have more to add?” question chains. Use it only in screener questions.
Do not nest it. A `MULTIFIELD` cannot appear inside another `MULTIFIELD` `groupedQuestionFields`.'

[log] ✔ Input field ScreenerQuestionBodyInput.multiselect description changed from:
```
Multiple-answer question. Displays as checkboxes.
```
To:
```
Multiple-answer question. Shows checkboxes.
```

[log] ✔ Input field ScreenerQuestionBodyInput.pageBreak description changed from:

Groups questions on a page. Questions between pagebreaks appear together.
Maximum: 20 questions per page. Default: 3 per page (desktop), all on one page (mobile).

To:

Groups questions on a page. Questions between page breaks appear together.
Maximum: 20 questions per page. Default: 3 per page on desktop, all on one page on mobile.

[log] ✔ Input field ScreenerQuestionBodyInput.select description changed from:

Multiple-choice question. Single answer only.
1-5 answers: radio buttons.
6+ answers: dropdown list.

To:

Multiple-choice question. Job seekers select one answer.
1–5 options: radio buttons. 6 or more: dropdown.

[log] ✔ Input field ScreenerQuestionBodyInput.text description changed from:

Short answer question. Displays as single-line text field.
Formats: integer, decimal, numeric_text.
See [JSON questions parameters](https://docs.indeed.com/indeed-apply/screener-questions#json-questions-parameters).

To:

Short answer. Shows a single-line text field.
Formats: `integer`, `decimal`, `numeric_text`.
See [JSON questions parameters](https://docs.indeed.com/indeed-apply/screener-questions#json-questions-parameters).

[log] ✔ Input field ScreenerQuestionBodyInput.textarea description changed from:
```
Long-form answer question. Displays as multi-line text field.
```
To:
```
Long-form answer. Shows a multi-line text field.
```

[log] ✔ Input field SeatIdentifierInput.jobKey description changed from:

Encrypted `jobPostId` for the seats `JobPost`. Returned by `addSeats` and also available on `EmployerJobSeatMetaData`.

To:

Encrypted `aggJobId` for the seat returned by [`addSeats`](/api/job/mutations/jobsIngest/addSeats).
Pass it to `SeatIdentifierInput.jobKey` in [`updateSeats`](/api/job/mutations/jobsIngest/updateSeats) or [`clearSeats`](/api/job/mutations/jobsIngest/clearSeats).
If the seat add failed, the value is null.'

[log] ✔ Description:

Salary for a seat. Use `maximumMinor` and `minimumMinor` for a range. For a fixed salary, set both fields to the same value.

On type SeatJobPostingSalaryInput has changed to:

Salary for a seat. Use `maximumMinor` and `minimumMinor` for a range. For a fixed salary, set both to the same value.

[log] ✔ Input field SeatLocationInput.country description changed from:

Country code. See [Supported language codes, country codes, and locales](https://docs.indeed.com/api/job/objects/CreateSourcedJobPostingInput#language-codes-and-locales).

To:

Country code. See [Supported language codes, country codes, and locales](https://docs.indeed.com/api/job/objects/CreateSourcedJobPostingInput#language-codes-and-locales).

[log] ✔ Input field SeatLocationInput.latitude description changed from:
```
Latitude for the job location.
```
To:
```
Latitude.
```
[log] ✔ Input field SeatLocationInput.longitude description changed from:
```
Longitude for the job location.
```
To:
```
Longitude.
```
[log] ✔ Input field SeatLocationInput.streetAddress description changed from:
```
Street address. Example: `1600 Pennsylvania Ave`.
```
To:
```
Street address. Example: `1600 Pennsylvania Ave`.
```

[log] ✔ Input field SeatTaxonomyInput.attributes description changed from:

Taxonomy attributes as [SUIDs](https://docs.indeed.com/getstarted/understanding-suids/#suid-format) or strings. Maximum 100 per seat.

To:

Taxonomy attributes as [SUIDs](https://docs.indeed.com/getstarted/understanding-suids/#suid-format) or strings. Maximum 100 per seat.

[log] ✔ Input field SeatTaxonomyInput.remoteType description changed from:

Location flexibility. Omit this field or set it to `null` for non-remote jobs.
Values: `Fully Remote`, `Hybrid Remote`.

To:

Location flexibility. Omit or set to null for non-remote jobs.
Values: `Fully Remote`, `Hybrid Remote`.

[log] ✔ Input field SelectQualificationQuestionInput.match description changed from:
```
Evaluation method: match.
```
To:
```
Match evaluation.
```
[log] ✔ Input field SelectQualificationQuestionInput.type description changed from:
```
Qualification type affecting the application in Indeed Apply.
```
To:
```
How the qualification affects the Indeed Apply application.
```

[log] ✔ Input field SelectQuestionInput.condition description changed from:

Conditional question. Depends on a previous answer. Specify the previous question ID and activating option value.
Example: if applicant answers yes to military service, show a follow-up question about branch of service.

To:

Show this question only when a previous answer matches. Set the previous question ID and the value that activates this question.
**Example**: If the applicant answers yes to military service, show a follow-up about branch of service.

[log] ✔ Input field SelectQuestionInput.required description changed from:

`true`: question is required. Unanswered optional questions return `"` (empty string). Default: `false`.

To:

If `true`, the question is required. Unanswered optional questions return `"`. Default: `false`.

[log] ✔ Input field SelectScreenerQuestionInput.qualification description changed from:

Qualification criterion for job requirements. Applicants must meet employer-defined conditions.
Non-blocking: all applications delivered regardless of meeting criteria.

To:

Qualification for this question. Indeed still delivers applications that do not meet the criterion (`NON_BLOCKING`).

[log] ✔ Description:

Return type for an accepted job posting. Accepted jobs are queued for indexing. Jobs violating [Job Posting Standards](https://indeedinc.my.site.com/employerSupport1/s/article/115005915763) might not appear on Indeed.

On type SourcedJobPosting has changed to:

Return type for an accepted job posting.
Accepted jobs are queued for indexing.
Jobs violating [Job Posting Standards](https://indeedinc.my.site.com/employerSupport1/s/article/115005915763) might not appear on Indeed.

[log] ✔ Field SourcedJobPosting.employerJobId description changed from:

The `EmployerJob` entity ID in base64-encoded [IRI](/getstarted/iris) format. Equivalent to `sourcedPostingId`. Use to query the posting as an `EmployerJob` through `node` and `nodes` queries.

To:

The `EmployerJob` entity ID in base64-encoded [IRI](/getstarted/iris) format.
Equivalent to `sourcedPostingId`.
Use to query the posting as an `EmployerJob` through `node` and `nodes` queries.

[log] ✔ Field SourcedJobPosting.sourcedPostingId description changed from:

UUID or Indeed Employer Job ID. Indeed generates this unique ID for each submitted job. Use this ID to expire the posting.

To:

UUID or Indeed Employer Job ID.
Indeed generates this unique ID for each submitted job. Use this ID to expire the posting.

[log] ✔ Input field SourcedJobPostingBodyInput.benefits description changed from:

List of job benefits. Specify each benefit as a separate string. Use an empty list if no non-salary benefits.

To:

List of job benefits. Specify each benefit as a separate string. Use an empty list if there are no non-salary benefits.

[log] ✔ Input field SourcedJobPostingBodyInput.description description changed from:

The job description shown to job seekers. Maximum `65,000` bytes (`1` byte for ASCII, `2` to `3` bytes for other characters). It must match the job posted at [`SourcedJobPostingMetadataInput.url`](/api/job/objects/SourcedJobPostingMetadataInput).
The default format is `TEXT`. HTML is optional, but if the URL points to HTML content, the `description` field must also use HTML.
For supported elements, see [Job description formatting](https://docs.indeed.com/job-sync-api/reference/job-description-formatting).

To:

The job description shown to job seekers.
* Plain text (`TEXT`): 30 to 20,000 characters. * HTML (`RICH_FORMATTING`): At least 30 characters and at most 65,000 UTF-8 bytes. Multibyte characters count toward the byte limit.
The description must match the job at [`SourcedJobPostingMetadataInput.url`](/api/job/objects/SourcedJobPostingMetadataInput).
If the client uses HTML on its job list or job details pages, Indeed requires `RICH_FORMATTING` for API jobs unless you have a good reason to omit it. HTML helps the job look closer to the client version. HTML has limits on attributes and element order.
`description` rejects supplementary characters for non-JP postings. JP postings are exempt.
See [Job description formatting](/job-sync-api/reference/job-description-formatting).

[log] ✔ Input field SourcedJobPostingBodyInput.descriptionFormatting description changed from:

Format of the job description. If the client uses HTML on its job list or job details pages, Indeed generally expects HTML for XML and API jobs unless there is a good reason not to include it.
Using HTML helps the job appear closer to the client version. Poor formatting can lead to complaints from clients and job seekers.
To provide the job description in HTML, set this field to `RICH_FORMATTING`. For more information, see [Job description formatting](/job-sync-api/reference/job-description-formatting). HTML has restrictions on attributes and element order.
Default: `TEXT`.

To:

Format of the job description.
To send HTML, set this field to `RICH_FORMATTING`. If the client uses HTML on its job list or job details pages, Indeed requires `RICH_FORMATTING` for API jobs unless you have a good reason to omit it. HTML helps the job look closer to the client version. Poor formatting can lead to complaints from clients and job seekers.
HTML has limits on attributes and element order. See [Job description formatting](/job-sync-api/reference/job-description-formatting).

[log] ✔ Input field SourcedJobPostingBodyInput.subtitle description changed from:
```
Job title subheader. Example: `A bright and pleasant workplace`
```
To:
```
Job title subheader.
**Example**: `A bright and pleasant workplace`
```

[log] ✔ Input field SourcedJobPostingFineGrainedJobSalaryInput.fixedOvertimePay description changed from:

Set to `true` when base salary includes overtime with no extra pay.
US: Some jobs are overtime-exempt. See [Fact Sheet #17A: Exemption for Executive, Administrative, Professional, Computer & Outside Sales Employees Under the Fair Labor Standards Act (FLSA)](https://www.dol.gov/agencies/whd/fact-sheets/17a-overtime).
Japan: Fixed overtime means overtime pay is included in salary. See [What is Fixed Overtime Pay?](https://www.nsasia.co.jp/jsj/jobseeker/knowledge/what-is-fixed-overtime-pay).

To:

Set to `true` when base salary includes overtime with no extra pay.
US: Some jobs are overtime-exempt.
See [Fact Sheet #17A: Exemption for Executive, Administrative, Professional, Computer & Outside Sales Employees Under the Fair Labor Standards Act (FLSA)](https://www.dol.gov/agencies/whd/fact-sheets/17a-overtime).
Japan: Fixed overtime means overtime pay is included in salary.
See [What is Fixed Overtime Pay?](https://www.nsasia.co.jp/jsj/jobseeker/knowledge/what-is-fixed-overtime-pay).

[log] ✔ Input field SourcedJobPostingFineGrainedJobSalaryInput.fixedOvertimeSalaryMinor description changed from:

Fixed overtime pay above base pay, in minor currency units. Must be greater than zero. Zero values can affect job visibility.
**Examples**: $102.50 → 10250, €102.50 → 10250, £102.50 → 10250, ¥10250 → 10250

To:

Fixed overtime pay above base pay, in minor currency units.
Must be greater than zero. Zero values can affect job visibility.
**Examples**: $102.50 → 10250, €102.50 → 10250, £102.50 → 10250, ¥10250 → 10250

[log] ✔ Input field SourcedJobPostingFineGrainedJobSalaryInput.totalSalaryMinor description changed from:

Total salary for the period, in minor currency units. Must be greater than zero. Zero values can affect job visibility.
**Examples**: $102.50 → 10250, €102.50 → 10250, £102.50 → 10250, ¥10250 → 10250

To:

Total salary for the period, in minor currency units.
Must be greater than zero. Zero values can affect job visibility.
**Examples**: $102.50 → 10250, €102.50 → 10250, £102.50 → 10250, ¥10250 → 10250

[log] ✔ Input field SourcedJobPostingIndeedApplyInput.resumeRequired description changed from:

Resume requirement:
- `YES` - Required (default) - `OPTIONAL` - Optional - `NO` - Hidden
If `OPTIONAL` or `NO`, screener questions are required. Support formats: .pdf, .doc, .docx, .rtf, .txt.

To:

Resume requirement:
- `YES` - Required (default) - `OPTIONAL` - Optional - `NO` - Hidden
If `OPTIONAL` or `NO`, screener questions are required. Supported formats: `.pdf`, `.doc`, `.docx`, `.rtf`, `.txt`.

[log] ✔ Input field SourcedJobPostingLocationInput.cityRegionPostal description changed from:

City, region (state, county, or prefecture), and postal code.
**Examples**: Washington, District of Columbia, 20500 (USA), 100-8994 東京都千代田区丸の内 (Japan), Mayfair, London, W1J (UK).

To:

City, region (state, county, or prefecture), and postal code.
**Examples**:
* Washington, District of Columbia, 20500 (USA)
* 100-8994 東京都千代田区丸の内 (Japan), Mayfair, London, W1J (UK)

[log] ✔ Input field SourcedJobPostingLocationInput.country description changed from:

Country code for the job location. See [Supported language codes, country codes, and locales](#supported-language-codes-country-codes-and-locales).
Corresponds to GIS admin0.

To:

Country code for the job location.
See [Supported language codes, country codes, and locales](/api/reference/language-and-country-codes).
Corresponds to GIS admin0.

[log] ✔ Input field SourcedJobPostingLocationInput.streetAddress description changed from:

Street address with street name and number. **Examples**: 1600 Pennsylvania Ave (USA), 2-7-2 (Japan).

To:

Street address with street name and number.
**Examples**: 1600 Pennsylvania Ave (USA), 2-7-2 (Japan).

[log] ✔ Input field SourcedJobPostingMetadataInput.datePublished description changed from:

Date the job is first published. Only set a future date if Indeed has approved delayed publishing. The date must match the date on your site.

To:

Date the job is first published. Only set a future date if Indeed has approved delayed publishing.
The date must match the date on your site.

[log] ✔ Input field SourcedJobPostingMetadataInput.jobPostingId description changed from:

Unique job ID in your ATS (reference number).
For jobs with seats, each `seatPostingId` becomes the job post reference number. The `jobPostingId` groups seats that become individual job posts.

To:

Unique job ID in your ATS (reference number).
For jobs with seats, each `seatPostingId` becomes the job post reference number.
The `jobPostingId` groups seats that become individual job posts.

[log] ✔ Input field SourcedJobPostingMetadataInput.numberOfHires description changed from:

Number of positions to fill. Leave null if unknown. Set to `-1` if undecided, to be determined later.

To:

Number of positions to fill. Omit or set to null if unknown. Set to `-1` if undecided.

[log] ✔ Input field SourcedJobPostingProbationaryPeriodInput.probationaryConditions description changed from:

Probationary period description. Include salary, hours, or employment type if different from regular terms.

To:

Probationary period description.
Include salary, hours, or employment type if different from regular terms.

[log] ✔ Description:

Structured salary information in minor currency units (cents for US, yen for Japan).
Use `maximumMinor` and `minimumMinor` for a range, set both to the same value for fixed salary, or set only `minimumMinor` for minimum-only salary.
`currency`: [ISO-4217 codes](https://en.wikipedia.org/wiki/ISO_4217#Active_codes_(List_One)) (USD, JPY).
`salaryFrequency`: hour, day, week, month, mile, or year.
Dont pass `0` in pay fields. Zero values can affect job visibility.

On type SourcedJobPostingSalaryInput has changed to:

Structured salary information in minor currency units (cents for US, yen for Japan).
Use `maximumMinor` and `minimumMinor` for a range.
Set both to the same value for fixed salary.
Set only `minimumMinor` for minimum-only salary.
`currency`: [ISO-4217 codes](https://en.wikipedia.org/wiki/ISO_4217#Active_codes_(List_One)) (USD, JPY).
`salaryFrequency`: hour, day, week, month, mile, or year.
Do not pass `0` in pay fields. Zero values can affect job visibility.'

[log] ✔ Input field SourcedJobPostingTaskBasedSalaryInput.taskDescription description changed from:

Task description. Max 65,000 bytes (1 byte per ASCII character; 2–3 bytes per other character).

To:

Task description.
Max 65,000 bytes (1 byte per ASCII character; 2–3 bytes per other character).

[log] ✔ Input field SourcedJobPostingTaxonomyInput.categories description changed from:

Job categories for search and sponsorship. Recommended for job management and displaying additional details (such as facility or department).

To:

Job categories for search and sponsorship.
Recommended for job management and displaying additional details (such as facility or department).

[log] ✔ Input field SourcedJobPostingTaxonomyInput.remoteType description changed from:

Location flexibility:
- `Fully Remote` - Remote only, no on-site work - `Hybrid Remote` - Mix of on-site and remote work
This field does not determine job location.
:::note
For non-remote and non-hybrid jobs, leave blank or set to null.
:::

To:

Location flexibility:
* `Fully Remote` - Remote only, no on-site work * `Hybrid Remote` - Mix of on-site and remote work
This field does not determine job location.
For non-remote and non-hybrid jobs, omit this field or set it to `null`.

[log] ✔ Description:

Return type for an accepted job update. Changes might not appear right away.

On type SourcedJobPostingUpdate has changed to:

Accepted job update. Changes might not appear right away.

[log] ✔ Field SourcedJobPostingUpdate.employerJobId description changed from:

Employer job ID, base64-encoded as an [IRI](/getstarted/iris).

To:

Employer job ID as a base64-encoded [IRI](/integration-basics/graphql-at-indeed/iris).

[log] ✔ Input field TextAreaQuestionInput.condition description changed from:

Conditional question. Depends on a previous answer. Specify the previous question ID and activating option value.
Example: if applicant answers yes to military service, show a follow-up question about branch of service.

To:

Show this question only when a previous answer matches. Set the previous question ID and the value that activates this question.
**Example**: If the applicant answers yes to military service, show a follow-up about branch of service.

[log] ✔ Input field TextAreaQuestionInput.required description changed from:

`true`: question is required. Unanswered optional questions return `"` (empty string). Default: `false`.

To:

If `true`, the question is required. Unanswered optional questions return `"`. Default: `false`.

[log] ✔ Input field TextAreaQuestionInput.validationRuleKey description changed from:

Optional key referencing an external validation rule. Enforced on the job seekers answer at apply time. Unknown keys are rejected at ingestion.

To:

Optional key for an external validation rule. Indeed enforces it on the job seekers answer at apply time. Unknown keys fail ingestion.

[log] ✔ Input field TextDecimalQualificationQuestionInput.range description changed from:

Evaluation method: `range`. Answers must fall within the defined min/max values.

To:

Range evaluation. The answer must fall between the min and max values.

[log] ✔ Input field TextDecimalQualificationQuestionInput.type description changed from:
```
Qualification type affecting the application in Indeed Apply.
```
To:
```
How the qualification affects the Indeed Apply application.
```
[log] ✔ Input field TextIntegerQualificationQuestionInput.range description changed from:
```
Evaluation method: range. Answers must fall within the defined min/max values.
```
To:
```
Range evaluation. The answer must fall between the min and max values.
```
[log] ✔ Input field TextIntegerQualificationQuestionInput.type description changed from:
```
Qualification type affecting the application in Indeed Apply.
```
To:
```
How the qualification affects the Indeed Apply application.
```
[log] ✔ Input field TextQuestionInput.decimal description changed from:
```
Decimal or floating-point answer question.
```
To:
```
Decimal or floating-point answer.
```
[log] ✔ Input field TextQuestionInput.freeform description changed from:
```
Freeform text answer question.
```
To:
```
Freeform text answer.
```
[log] ✔ Input field TextQuestionInput.integer description changed from:
```
Integer answer question.
```
To:
```
Integer answer.
```

[log] ✔ Input field TextQuestionInput.numeric description changed from:

Numeric text answer question (that is, identifiers with leading zeros).

To:

Numeric text answer (for example, identifiers with leading zeros).

[log] ✔ Input field TextScreenerQuestionInput.decimal description changed from:
```
Accepts numbers. Allows leading zeros and decimals.
```
To:
```
Numeric answers. Allows leading zeros and decimals.
```
[log] ✔ Input field TextScreenerQuestionInput.freeform description changed from:
```
Accepts text answers.
```
To:
```
Text answers.
```
[log] ✔ Input field TextScreenerQuestionInput.integer description changed from:
```
Integer-only question. No decimals or leading zeros.
```
To:
```
Integer answers only. No decimals or leading zeros.
```
[log] ✔ Input field TextScreenerQuestionInput.numeric description changed from:
```
Accepts numbers only. No decimals.
```
To:
```
Numeric answers only. No decimals.
```

[log] ✔ Description:

Seat body for updating a seat. All fields are optional. Provide only changed fields.

On type UpdateSeatBodyInput has changed to:

Body data for a seat update. All fields are optional. Provide only changed fields.

[log] ✔ Input field UpdateSeatBodyInput.location description changed from:

Updated location. Omit or set to `null` for no change.

To:

Updated location. To leave the value unchanged, omit this field or set it to null.

[log] ✔ Input field UpdateSeatBodyInput.salary description changed from:

Updated salary. Omit or set to `null` for no change.

To:

Updated salary. To leave the value unchanged, omit this field or set it to null.

[log] ✔ Description:
```
One seat update operation.
```
On type UpdateSeatInput has changed to:
```
One seat to update.
```
[log] ✔ Input field UpdateSeatInput.body description changed from:
```
Seat body data. Omit fields for no change.
```
To:
```
Seat body. To leave the value unchanged, omit this field or set it to null.
```
[log] ✔ Input field UpdateSeatInput.metadata description changed from:
```
Seat metadata. Omit fields for no change.
```
To:
```
Seat metadata. To leave the value unchanged, omit this field or set it to null.
```
[log] ✔ Description:
```
Seat metadata for updating a seat.
```
On type UpdateSeatMetadataInput has changed to:
```
Metadata for a seat update.
```
[log] ✔ Input field UpdateSeatMetadataInput.taxonomyClassification description changed from:
```
Taxonomy classification for the seat.
```
To:
```
Taxonomy classification.
```

[log] ✔ Input field UpdateSeatMetadataInput.trackingUrl description changed from:

Tracking URL for the seat. Omit or set to `null` for no change.

To:

Tracking URL. To leave the value unchanged, omit this field or set it to null.

[log] ✔ Input field UpdateSeatMetadataInput.url description changed from:
```
Job URL for the seat. Omit or set to `null` for no change.
```
To:
```
Job URL. To leave the value unchanged, omit this field or set it to null.
```
[log] ✔ Field UpdateSeatResult.employerJobId description changed from:
```
Base64-encoded IRI of the employer job.
```
To:
```
Employer job ID as a base64-encoded IRI.
```

[log] ✔ Field UpdateSeatResult.jobKey description changed from:

Encrypted `aggJobId` for the seat.

To:

Encrypted `aggJobId` for the seat returned by [`addSeats`](/api/job/mutations/jobsIngest/addSeats).
Pass it to `SeatIdentifierInput.jobKey` in [`updateSeats`](/api/job/mutations/jobsIngest/updateSeats) or [`clearSeats`](/api/job/mutations/jobsIngest/clearSeats).
If the seat add failed, the value is null.

[log] ✔ Field UpdateSeatResult.sourcedPostingId description changed from:
```
UUID form of the employer job ID.
```
To:
```
Employer job ID as a UUID.
```
[log] ✔ Description:
```
`updateSeats` input.
```
On type UpdateSeatsInput has changed to:
```
Input for `updateSeats`.
```
[log] ✔ Description:
```
Return type for `updateSeats`.
```
On type UpdateSeatsPayload has changed to:
```
Payload for `updateSeats`.
```

[log] ✔ Description:

Updated job body. See [`UpdateSourcedJobPostingInput.body`](https://docs.indeed.com/api/job/objects/UpdateSourcedJobPostingInput).

On type UpdateSourcedJobPostingBodyInput has changed to:

Updated job body. See [`UpdateSourcedJobPostingInput.body`](https://docs.indeed.com/api/job/objects/UpdateSourcedJobPostingInput).

[log] ✔ Input field UpdateSourcedJobPostingBodyInput.companyName description changed from:

Company name. Maximum 200 characters. Omit or set to `null` for no change.

To:

Company name. Maximum 200 characters. To leave the value unchanged, omit this field or set it to null.

[log] ✔ Input field UpdateSourcedJobPostingBodyInput.description description changed from:

Job description. 30 to 20,000 characters. Omit or set to `null` for no change.

To:

Job description shown to job seekers.
* Plain text (`TEXT`): 30 to 20,000 characters. * HTML (`HTML`): at least 30 characters, at most 65,000 [UTF-8](https://www.rfc-editor.org/info/rfc3629/) bytes. Multibyte characters count toward the byte limit.
To leave the value unchanged, omit this field or set it to null. Must match the job at [`SourcedJobPostingMetadataInput.url`](/api/job/objects/SourcedJobPostingMetadataInput).
If the client uses HTML on job list or details pages, Indeed requires HTML for XML and API jobs unless there is a good reason not to. To send HTML, set `descriptionFormatting` to `RICH_FORMATTING`. See [Job description formatting](/job-sync-api/reference/job-description-formatting).

[log] ✔ Input field UpdateSourcedJobPostingBodyInput.descriptionFormatting description changed from:

Description format. Omit to use the default `TEXT`.

To:

Job description format. To send HTML, set this field to `RICH_FORMATTING`.
See [Job description formatting](/job-sync-api/reference/job-description-formatting).

[log] ✔ Input field UpdateSourcedJobPostingBodyInput.jobLocation description changed from:
```
Job location. Omit or set to `null` for no change.
```
To:
```
Job location. To leave the value unchanged, omit this field or set it to null.
```

[log] ✔ Input field UpdateSourcedJobPostingBodyInput.salary description changed from:

Job salary. Omit or set to `null` for no change.

To:

Job salary. To leave the value unchanged, omit this field or set it to null.
Every non-null `salary` object must include `period`, including when `maximumMinor` or `minimumMinor` is set to null to clear a value.

[log] ✔ Input field UpdateSourcedJobPostingBodyInput.title description changed from:

Job title. Maximum 75 characters. Omit or set to `null` for no change.

To:

Job title. Maximum 75 characters. To leave the value unchanged, omit this field or set it to null.

[log] ✔ Object type UpdateSourcedJobPostingGeneralLocationInput has description:
```
City, region, postal code, and optional street address.
```
[log] ✔ Input field UpdateSourcedJobPostingGeneralLocationInput.streetAddress description changed from:
```
Street address of the job location.
Example: `1600 Pennsylvania Ave`.
```
To:
```
Street address.
Example: `1600 Pennsylvania Ave`.
```
[log] ✔ Description:
```
Job posting update input.
```
On type UpdateSourcedJobPostingInput has changed to:
```
One job posting update.
```

[log] ✔ Input field UpdateSourcedJobPostingInput.sourcedPostingId description changed from:

Employer job UUID from `createSourcedJobPostings`. Also accepts a base64-encoded IRI from `EmployerJob`.

To:

Employer job UUID from `createSourcedJobPostings`.
Also accepts a base64-encoded [IRI](/integration-basics/graphql-at-indeed/iris) from `EmployerJob`.

[log] ✔ Description:
```
Job location update. Provide one field or the API returns an error.
```
On type UpdateSourcedJobPostingLocationInput has changed to:
```
Job location update. Provide one field or the API returns an error.
```
[log] ✔ Input field UpdateSourcedJobPostingLocationInput.general description changed from:
```
General location input. Accepts values from `cityRegionPostal` to specific addresses.
```
To:
```
General location, from `cityRegionPostal` to a specific address.
```

[log] ✔ Description:

Job metadata to update. Provide at least one field.
Not atomic. Errors can cause partial updates.

On type UpdateSourcedJobPostingMetadataInput has changed to:

Job metadata to update. Not atomic. Errors can cause partial updates.

[log] ✔ Input field UpdateSourcedJobPostingMetadataInput.trackingUrl description changed from:
```
Job tracking URL.
```
To:
```
Tracking URL.
```
[log] ✔ Description:
```
Return type for each `updateSourcedJobPostings` result.
```
On type UpdateSourcedJobPostingResult has changed to:
```
Result for one `updateSourcedJobPostings` operation.
```
[log] ✔ Field UpdateSourcedJobPostingResult.jobPosting description changed from:
```
Updated job posting, or null if the update was not accepted.
```
To:
```
Updated job posting. Null if the update was not accepted.
```
[log] ✔ Object type UpdateSourcedJobPostingSalaryInput has description:
```
Salary update.
```

[log] ✔ Input field UpdateSourcedJobPostingSalaryInput.currency description changed from:

Salary currency in ISO 4217 format, such as `USD`. Omit or set to `null` for no change.

To:

Salary currency in ISO 4217 format, such as `USD`.
To leave the value unchanged, omit this field or set it to null.

[log] ✔ Input field UpdateSourcedJobPostingSalaryInput.maximumMinor description changed from:

Maximum amount in local minor currency. Omit or set to `null` to clear.

To:

Maximum amount in local minor currency. To clear, omit this field or set it to null.
Every non-null `salary` object must include `period`, including when `maximumMinor` is set to null to clear a value.

[log] ✔ Input field UpdateSourcedJobPostingSalaryInput.minimumMinor description changed from:

Minimum amount in local minor currency. Omit or set to `null` to clear.

To:

Minimum amount in local minor currency. To clear, omit this field or set it to null.
Every non-null `salary` object must include `period`, including when `minimumMinor` is set to null to clear a value.

[log] ✔ Input field UpdateSourcedJobPostingSalaryInput.period description changed from:

Salary period.

To:

Salary period.
Every non-null `salary` object must include `period`, including when `maximumMinor` or `minimumMinor` is set to null to clear a value.

[log] ✔ Description:
```
`updateSourcedJobPostings` input.
```
On type UpdateSourcedJobPostingsInput has changed to:
```
Input for `updateSourcedJobPostings`.
```
[log] ✔ Description:
```
Return type for `updateSourcedJobPostings`.
```
On type UpdateSourcedJobPostingsPayload has changed to:
```
Payload for `updateSourcedJobPostings`.
```

[log] ✔ Field UpdateSourcedJobPostingsPayload.results description changed from:

Results for each update. Array items are never null, but `jobPosting` is null if the update was not accepted.

To:

Results for each update. Array items are never null.
`jobPosting` is null if the update was not accepted.

[log] ✔ Description:

Well-formed URL. Specifcation: [RFC 2396/2732](https://en.wikipedia.org/wiki/Uniform_Resource_Identifier)

On type WebUrl has changed to:

A well-formed URL ([RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986)).

GraphQL schema change log: 2026-08-24​

Was this page helpful?

GraphQL schema change log: 2026-08-24