2026-08-24
GraphQL schema change log: 2026-08-24
📘 Documentation: Updated the GraphQL schema and the GraphQL API Reference with these changes:
-
Added input field
jobRequisitionIdof type[String!]to input object typeFindEmployerJobsPartnerFilterInput -
Changed the description of type
AddSeatBodyInputfrom:Seat body for adding a seat.To:
Body data for a new seat. -
Changed the description of input field
AddSeatBodyInput.locationfrom:Location for the seat.To:
Seat location. -
Changed the description of input field
AddSeatBodyInput.salaryfrom:Salary for the seat.To:
Seat salary. -
Changed the description of type
AddSeatInputfrom:One seat add operation.To:
One seat to add. -
Changed the description of input field
AddSeatInput.bodyfrom:Seat body data.To:
Seat body. -
Changed the description of input field
AddSeatInput.seatPostingIdfrom: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. -
Changed the description of type
AddSeatMetadataInputfrom:Seat metadata for adding a seat.To:
Metadata for a new seat. -
Changed the description of input field
AddSeatMetadataInput.taxonomyClassificationfrom:Taxonomy classification for the seat.To:
Taxonomy classification. -
Changed the description of input field
AddSeatMetadataInput.trackingUrlfrom:Tracking URL for the seat.To:
Tracking URL. -
Changed the description of input field
AddSeatMetadataInput.urlfrom:Job URL for the seat.To:
Job URL. -
Changed the description of type
AddSeatResultfrom:Result for one seat add operation.To:
Result for one seat add. -
Changed the description of field
AddSeatResult.employerJobIdfrom:Base64-encoded IRI of the employer job.To:
Employer job ID as a base64-encoded IRI. -
Changed the description of field
AddSeatResult.jobKeyfrom: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. -
Changed the description of field
AddSeatResult.seatPostingIdfrom:Agency-provided seat identifier.To:
Agency-provided seat ID. -
Changed the description of field
AddSeatResult.sourcedPostingIdfrom:UUID form of the employer job ID.To:
Employer job ID as a UUID. -
Changed the description of type
AddSeatsInputfrom:`addSeats` input.To:
Input for `addSeats`. -
Changed the description of type
AddSeatsPayloadfrom:`addSeats` return type.To:
Payload for `addSeats`. -
Changed the description of type
ClearSeatInputfrom:One seat clear operation.To:
One seat to remove. -
Changed the description of input field
ClearSeatInput.seatIdentifierfrom:Seat to remove. Provide one field.To:
Seat to remove. Provide one field. -
Changed the description of type
ClearSeatResultfrom:Result for one seat clear operation.To:
Result for one seat clear. -
Changed the description of field
ClearSeatResult.employerJobIdfrom:Base64-encoded IRI of the employer job.To:
Employer job ID as a base64-encoded IRI. -
Changed the description of field
ClearSeatResult.jobKeyfrom: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. -
Changed the description of field
ClearSeatResult.seatPostingIdfrom:Agency-provided seat identifier.To:
Agency-provided seat ID. -
Changed the description of field
ClearSeatResult.sourcedPostingIdfrom:UUID form of the employer job ID.To:
Employer job ID as a UUID. -
Changed the description of type
ClearSeatsInputfrom:`clearSeats` input.To:
Input for `clearSeats`. -
Changed the description of input field
ClearSeatsInput.seatRemovalsfrom:Seat removals to process. Accepts one item.To:
Seat removals to process. Accepts one item. -
Changed the description of type
ClearSeatsPayloadfrom:`clearSeats` return type.To:
Payload for `clearSeats`. -
Changed the description of type
ClearSourcedJobPostingUpdateInputfrom:Clears updates from `updateSourcedJobPostings`.Not atomic. Errors can partially clear updates.To:
One job posting with updates from `updateSourcedJobPostings` to clear. Not atomic. Errors can partially clear updates. -
Changed the description of input field
ClearSourcedJobPostingUpdateInput.sourcedPostingIdfrom: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). -
Changed the description of type
ClearSourcedJobPostingUpdateResultfrom:Return type for each `clearJobPostingUpdates` result.To:
Result for one `clearSourcedJobPostingUpdates` operation. -
Changed the description of field
ClearSourcedJobPostingUpdateResult.jobPostingfrom:The cleared job posting, or null if nothing was cleared.To:
Cleared job posting. If nothing was cleared, null. -
Changed the description of type
ClearSourcedJobPostingUpdatesInputfrom:`clearSourcedJobPostingUpdates` input.To:
Input for `clearSourcedJobPostingUpdates`. -
Changed the description of type
ClearSourcedJobPostingUpdatesPayloadfrom:Return type for `clearSourcedJobPostingUpdates`.To:
Payload for `clearSourcedJobPostingUpdates`. -
Changed the description of field
ClearSourcedJobPostingUpdatesPayload.resultsfrom: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. -
Changed the description of input field
ConditionConstraintInput.valuesfrom:Values that satisfy the condition when the id question matches.To:
Values that satisfy the condition when that question matches. -
Changed the description of type
CreateSourcedJobPostingResultfrom:Intermediary type. A null `jobPosting` indicates a creation error. The GraphQL `errors` object shows the problem by index.To:
Intermediary type. If a creation error occurs, `jobPosting` is null.The GraphQL `errors` array shows the problem by index. -
Changed the description of field
CreateSourcedJobPostingsPayload.resultsfrom: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. -
Changed the description of input field
DateQuestionInput.conditionfrom: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. -
Changed the description of input field
DateQuestionInput.formatfrom: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. -
Changed the description of input field
DateQuestionInput.requiredfrom:`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`. -
Changed the description of input field
DateQuestionQualificationInput.rangefrom: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. -
Changed the description of input field
DateQuestionQualificationInput.typefrom:Qualification type affecting the application in Indeed Apply.To:
How the qualification affects the Indeed Apply application. -
Changed the description of input field
DateScreenerQuestionInput.qualificationfrom: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`). -
Changed the description of type
DateTimefrom:Date with time (isoformat)To:
Datetime as [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339). -
Changed the description of input field
DecimalTextQuestionInput.conditionfrom: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. -
Changed the description of input field
DecimalTextQuestionInput.requiredfrom:`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`. -
Changed the description of input field
DecimalTextScreenerQuestionInput.qualificationfrom: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`). -
Changed the description of type
DemographicQuestionsBodyInputfrom: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.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). -
Changed the description of input field
DemographicQuestionsBodyInput.datefrom: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. -
Changed the description of input field
DemographicQuestionsBodyInput.informationfrom: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). -
Changed the description of input field
DemographicQuestionsBodyInput.multiselectfrom:Multiple-answer question. Displays as checkboxes.To:
Multiple-answer question. Shows checkboxes. -
Changed the description of input field
DemographicQuestionsBodyInput.pageBreakfrom: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. -
Changed the description of input field
DemographicQuestionsBodyInput.selectfrom: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. -
Changed the description of input field
DemographicQuestionsBodyInput.textfrom: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). -
Changed the description of input field
DemographicQuestionsBodyInput.textareafrom:Long-form answer question. Displays as multi-line text field.To:
Long-form answer. Shows a multi-line text field. -
Changed the description of type
EmployerJobIdentifierInputfrom:Identifies the employer job. Provide exactly one field: `sourcedPostingId` as a UUID, or `employerJobId` as a base64-encoded IRI.To:
Identifies the employer job. Provide exactly one field: `sourcedPostingId` as a UUID, or `employerJobId` as a base64-encoded IRI. -
Changed the description of input field
EmployerJobIdentifierInput.employerJobIdfrom:Base64-encoded IRI from `EmployerJob`. Accepts values from `createSourcedJobPostings` or `EmployerJob`.To:
Base64-encoded IRI from `EmployerJob`. Accepts values from `createSourcedJobPostings` or `EmployerJob`. -
Changed the description of type
ExpireSourcedJobBySourcedPostingIdInputfrom:Input containing Indeed Employer Job ID.To:
Input containing Indeed Employer job ID. -
Changed the description of input field
ExpireSourcedJobBySourcedPostingIdInput.sourcedPostingIdfrom: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. -
Changed the description of field
ExpireSourcedJobResult.inputDatafrom:Input values for this result. Is null on error.To:
Input values for this result. Null on error. -
Changed the description of field
ExpireSourcedJobsBySourcedPostingIdPayload.resultsfrom:Input for `expireSourcedJobsBySourcedPostingId` mutation.To:
Expiration results. -
Changed the description of input field
FileQuestionInput.conditionfrom: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. -
Changed the description of input field
FileQuestionInput.requiredfrom:`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`. -
Changed the description of input field
FreeformTextQuestionInput.conditionfrom: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. -
Changed the description of input field
FreeformTextQuestionInput.requiredfrom:`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`. -
Changed the description of input field
FreeformTextQuestionInput.validationRuleKeyfrom: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. -
Changed the description of type
HideFromIndeedSearchInputfrom: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.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. -
Changed the description of input field
HierarchicalOptionInput.conditionfrom: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. -
Changed the description of input field
HierarchicalQuestionInput.conditionfrom: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. -
Changed the description of input field
HierarchicalQuestionInput.hierarchicalOptionsfrom: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. -
Changed the description of input field
HierarchicalQuestionInput.requiredfrom:`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`. -
Changed the description of type
IndeedApplyConfigurationResumeFieldfrom:Resume field requirement values. See [Indeed Resume JSON object fields](https://docs.indeed.com/indeed-apply/application-data#indeed-resume-json-object-fields).To:
Resume field requirement values.See [Indeed Resume JSON object fields](https://docs.indeed.com/indeed-apply/application-data#indeed-resume-json-object-fields). -
Changed the description of input field
IndeedApplyQuestionsDetailsInput.questionsfrom: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). -
Changed the description of input field
IndeedApplyScreenerQuestionsDefinitionInput.demographicQuestionsfrom: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). -
Changed the description of input field
IndeedApplyScreenerQuestionsDefinitionInput.screenerQuestionsfrom: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. -
Changed the description of input field
InformationQuestionInput.conditionfrom: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. -
Changed the description of input field
IntegerTextQuestionInput.conditionfrom: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. -
Changed the description of input field
IntegerTextQuestionInput.requiredfrom:`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`. -
Changed the description of input field
IntegerTextScreenerQuestionInput.qualificationfrom: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`). -
Object type
JobsIngestMutationshas description:Job ingest mutations. -
Changed the description of argument
inputon fieldJobsIngestMutations.addSeatsfrom:nullTo:
Seat-add input. -
Changed the description of field
JobsIngestMutations.clearSeatsfrom:Clears or expires seats from a job.To:
Clears or expires seats on a job. -
Changed the description of argument
inputon fieldJobsIngestMutations.clearSeatsfrom:nullTo:
Seat-clear input. -
Changed the description of argument
inputon fieldJobsIngestMutations.clearSourcedJobPostingUpdatesfrom:nullTo:
Clear-updates input. -
Changed the description of field
JobsIngestMutations.createSourcedJobPostingsfrom: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. -
Changed the description of argument
inputon fieldJobsIngestMutations.updateSeatsfrom:nullTo:
Seat-update input. -
Changed the description of field
JobsIngestMutations.updateSourcedJobPostingsfrom: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. -
Changed the description of argument
inputon fieldJobsIngestMutations.updateSourcedJobPostingsfrom:nullTo:
Job posting update input. -
Changed the description of enum value
MatchStrategy.ALLfrom:Answer must match all provided values.To:
The answer must match all provided values. -
Changed the description of enum value
MatchStrategy.ANYfrom:Answer can match any provided value.To:
The answer can match any provided value. -
Changed the description of input field
MultiSelectQualificationQuestionInput.matchfrom:Evaluation method: match.To:
Match evaluation. -
Changed the description of input field
MultiSelectQualificationQuestionInput.typefrom:Qualification type affecting the application in Indeed Apply.To:
How the qualification affects the Indeed Apply application. -
Changed the description of input field
MultifieldQuestionInput.addButtonLabelfrom:Label on the Add another button (e.g., Add Another Job).To:
Label on the add button. For example, `Add Another Job`. -
Changed the description of input field
MultifieldQuestionInput.conditionfrom: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. -
Changed the description of input field
MultifieldQuestionInput.groupLabelfrom:Label shown above each entry group (e.g., Work Experience).To:
Label above each entry group. For example, `Work Experience`. -
Changed the description of input field
MultifieldQuestionInput.groupedQuestionFieldsfrom: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`. -
Changed the description of input field
MultifieldQuestionInput.maxEntryCountfrom: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`. -
Changed the description of input field
MultifieldQuestionInput.minEntryCountfrom: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`. -
Changed the description of type
MultiselectQuestionInputfrom:<!--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-->To:
Multiple-answer question. -
Changed the description of input field
MultiselectQuestionInput.conditionfrom: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. -
Changed the description of input field
MultiselectQuestionInput.requiredfrom:`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`. -
Changed the description of input field
MultiselectScreenerQuestionInput.qualificationfrom: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`). -
Changed the description of input field
NumericTextQuestionInput.conditionfrom: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. -
Changed the description of input field
NumericTextQuestionInput.requiredfrom:`true`: question is required. Unanswered optional questions return `"`.To:
If `true`, the question is required. Unanswered optional questions return `"`. Default: `false`. -
Changed the description of input field
NumericTextQuestionInput.validationRuleKeyfrom: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. -
Changed the description of input field
QualificationMatchAnyTextConfigurationInput.valuesfrom:Values applicant must match.To:
Values the applicant must match. -
Changed the description of input field
QualificationMultiValueTextMatchConfigurationInput.typefrom:Whether answer must match any or all provided values.To:
Whether the answer must match any or all provided values. -
Changed the description of input field
QualificationMultiValueTextMatchConfigurationInput.valuesfrom:Values applicant must match.To:
Values the applicant must match. -
Changed the description of enum value
QuestionQualificationImplicationType.NON_BLOCKINGfrom: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. -
Changed the description of type
ScreenerQuestionBodyInputfrom: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.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). -
Changed the description of input field
ScreenerQuestionBodyInput.datefrom: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. -
Changed the description of input field
ScreenerQuestionBodyInput.filefrom: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, txtTo:
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` -
Changed the description of input field
ScreenerQuestionBodyInput.hierarchicalfrom: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. -
Changed the description of input field
ScreenerQuestionBodyInput.informationfrom: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). -
Changed the description of input field
ScreenerQuestionBodyInput.multifieldfrom: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`.' -
Changed the description of input field
ScreenerQuestionBodyInput.multiselectfrom:Multiple-answer question. Displays as checkboxes.To:
Multiple-answer question. Shows checkboxes. -
Changed the description of input field
ScreenerQuestionBodyInput.pageBreakfrom: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. -
Changed the description of input field
ScreenerQuestionBodyInput.selectfrom: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. -
Changed the description of input field
ScreenerQuestionBodyInput.textfrom: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). -
Changed the description of input field
ScreenerQuestionBodyInput.textareafrom:Long-form answer question. Displays as multi-line text field.To:
Long-form answer. Shows a multi-line text field. -
Changed the description of input field
SeatIdentifierInput.jobKeyfrom: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.' -
Changed the description of type
SeatJobPostingSalaryInputfrom:Salary for a seat. Use `maximumMinor` and `minimumMinor` for a range. For a fixed salary, set both fields to the same value.To:
Salary for a seat. Use `maximumMinor` and `minimumMinor` for a range. For a fixed salary, set both to the same value. -
Changed the description of input field
SeatLocationInput.countryfrom: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). -
Changed the description of input field
SeatLocationInput.latitudefrom:Latitude for the job location.To:
Latitude. -
Changed the description of input field
SeatLocationInput.longitudefrom:Longitude for the job location.To:
Longitude. -
Changed the description of input field
SeatLocationInput.streetAddressfrom:Street address. Example: `1600 Pennsylvania Ave`.To:
Street address. Example: `1600 Pennsylvania Ave`. -
Changed the description of input field
SeatTaxonomyInput.attributesfrom: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. -
Changed the description of input field
SeatTaxonomyInput.remoteTypefrom: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`. -
Changed the description of input field
SelectQualificationQuestionInput.matchfrom:Evaluation method: match.To:
Match evaluation. -
Changed the description of input field
SelectQualificationQuestionInput.typefrom:Qualification type affecting the application in Indeed Apply.To:
How the qualification affects the Indeed Apply application. -
Changed the description of input field
SelectQuestionInput.conditionfrom: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. -
Changed the description of input field
SelectQuestionInput.requiredfrom:`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`. -
Changed the description of input field
SelectScreenerQuestionInput.qualificationfrom: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`). -
Changed the description of type
SourcedJobPostingfrom: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.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. -
Changed the description of field
SourcedJobPosting.employerJobIdfrom: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. -
Changed the description of field
SourcedJobPosting.sourcedPostingIdfrom: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. -
Changed the description of input field
SourcedJobPostingBodyInput.benefitsfrom: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. -
Changed the description of input field
SourcedJobPostingBodyInput.descriptionfrom: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). -
Changed the description of input field
SourcedJobPostingBodyInput.descriptionFormattingfrom: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). -
Changed the description of input field
SourcedJobPostingBodyInput.subtitlefrom:Job title subheader. Example: `A bright and pleasant workplace`To:
Job title subheader.**Example**: `A bright and pleasant workplace` -
Changed the description of input field
SourcedJobPostingFineGrainedJobSalaryInput.fixedOvertimePayfrom: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). -
Changed the description of input field
SourcedJobPostingFineGrainedJobSalaryInput.fixedOvertimeSalaryMinorfrom: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 → 10250To:
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 -
Changed the description of input field
SourcedJobPostingFineGrainedJobSalaryInput.totalSalaryMinorfrom: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 → 10250To:
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 -
Changed the description of input field
SourcedJobPostingIndeedApplyInput.resumeRequiredfrom:Resume requirement:- `YES` - Required (default) - `OPTIONAL` - Optional - `NO` - HiddenIf `OPTIONAL` or `NO`, screener questions are required. Support formats: .pdf, .doc, .docx, .rtf, .txt.To:
Resume requirement:- `YES` - Required (default) - `OPTIONAL` - Optional - `NO` - HiddenIf `OPTIONAL` or `NO`, screener questions are required. Supported formats: `.pdf`, `.doc`, `.docx`, `.rtf`, `.txt`. -
Changed the description of input field
SourcedJobPostingLocationInput.cityRegionPostalfrom: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) -
Changed the description of input field
SourcedJobPostingLocationInput.countryfrom: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. -
Changed the description of input field
SourcedJobPostingLocationInput.streetAddressfrom: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). -
Changed the description of input field
SourcedJobPostingMetadataInput.datePublishedfrom: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. -
Changed the description of input field
SourcedJobPostingMetadataInput.jobPostingIdfrom: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. -
Changed the description of input field
SourcedJobPostingMetadataInput.numberOfHiresfrom: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. -
Changed the description of input field
SourcedJobPostingProbationaryPeriodInput.probationaryConditionsfrom: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. -
Changed the description of type
SourcedJobPostingSalaryInputfrom: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.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.' -
Changed the description of input field
SourcedJobPostingTaskBasedSalaryInput.taskDescriptionfrom: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). -
Changed the description of input field
SourcedJobPostingTaxonomyInput.categoriesfrom: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). -
Changed the description of input field
SourcedJobPostingTaxonomyInput.remoteTypefrom:Location flexibility:- `Fully Remote` - Remote only, no on-site work - `Hybrid Remote` - Mix of on-site and remote workThis field does not determine job location.:::noteFor 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 workThis field does not determine job location.For non-remote and non-hybrid jobs, omit this field or set it to `null`. -
Changed the description of type
SourcedJobPostingUpdatefrom:Return type for an accepted job update. Changes might not appear right away.To:
Accepted job update. Changes might not appear right away. -
Changed the description of field
SourcedJobPostingUpdate.employerJobIdfrom: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). -
Changed the description of input field
TextAreaQuestionInput.conditionfrom: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. -
Changed the description of input field
TextAreaQuestionInput.requiredfrom:`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`. -
Changed the description of input field
TextAreaQuestionInput.validationRuleKeyfrom: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. -
Changed the description of input field
TextDecimalQualificationQuestionInput.rangefrom: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. -
Changed the description of input field
TextDecimalQualificationQuestionInput.typefrom:Qualification type affecting the application in Indeed Apply.To:
How the qualification affects the Indeed Apply application. -
Changed the description of input field
TextIntegerQualificationQuestionInput.rangefrom: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. -
Changed the description of input field
TextIntegerQualificationQuestionInput.typefrom:Qualification type affecting the application in Indeed Apply.To:
How the qualification affects the Indeed Apply application. -
Changed the description of input field
TextQuestionInput.decimalfrom:Decimal or floating-point answer question.To:
Decimal or floating-point answer. -
Changed the description of input field
TextQuestionInput.freeformfrom:Freeform text answer question.To:
Freeform text answer. -
Changed the description of input field
TextQuestionInput.integerfrom:Integer answer question.To:
Integer answer. -
Changed the description of input field
TextQuestionInput.numericfrom:Numeric text answer question (that is, identifiers with leading zeros).To:
Numeric text answer (for example, identifiers with leading zeros). -
Changed the description of input field
TextScreenerQuestionInput.decimalfrom:Accepts numbers. Allows leading zeros and decimals.To:
Numeric answers. Allows leading zeros and decimals. -
Changed the description of input field
TextScreenerQuestionInput.freeformfrom:Accepts text answers.To:
Text answers. -
Changed the description of input field
TextScreenerQuestionInput.integerfrom:Integer-only question. No decimals or leading zeros.To:
Integer answers only. No decimals or leading zeros. -
Changed the description of input field
TextScreenerQuestionInput.numericfrom:Accepts numbers only. No decimals.To:
Numeric answers only. No decimals. -
Changed the description of type
UpdateSeatBodyInputfrom:Seat body for updating a seat. All fields are optional. Provide only changed fields.To:
Body data for a seat update. All fields are optional. Provide only changed fields. -
Changed the description of input field
UpdateSeatBodyInput.locationfrom: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. -
Changed the description of input field
UpdateSeatBodyInput.salaryfrom: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. -
Changed the description of type
UpdateSeatInputfrom:One seat update operation.To:
One seat to update. -
Changed the description of input field
UpdateSeatInput.bodyfrom:Seat body data. Omit fields for no change.To:
Seat body. To leave the value unchanged, omit this field or set it to null. -
Changed the description of input field
UpdateSeatInput.metadatafrom:Seat metadata. Omit fields for no change.To:
Seat metadata. To leave the value unchanged, omit this field or set it to null. -
Changed the description of type
UpdateSeatMetadataInputfrom:Seat metadata for updating a seat.To:
Metadata for a seat update. -
Changed the description of input field
UpdateSeatMetadataInput.taxonomyClassificationfrom:Taxonomy classification for the seat.To:
Taxonomy classification. -
Changed the description of input field
UpdateSeatMetadataInput.trackingUrlfrom: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. -
Changed the description of input field
UpdateSeatMetadataInput.urlfrom: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. -
Changed the description of field
UpdateSeatResult.employerJobIdfrom:Base64-encoded IRI of the employer job.To:
Employer job ID as a base64-encoded IRI. -
Changed the description of field
UpdateSeatResult.jobKeyfrom: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. -
Changed the description of field
UpdateSeatResult.sourcedPostingIdfrom:UUID form of the employer job ID.To:
Employer job ID as a UUID. -
Changed the description of type
UpdateSeatsInputfrom:`updateSeats` input.To:
Input for `updateSeats`. -
Changed the description of type
UpdateSeatsPayloadfrom:Return type for `updateSeats`.To:
Payload for `updateSeats`. -
Changed the description of type
UpdateSourcedJobPostingBodyInputfrom:Updated job body. See [`UpdateSourcedJobPostingInput.body`](https://docs.indeed.com/api/job/objects/UpdateSourcedJobPostingInput).To:
Updated job body. See [`UpdateSourcedJobPostingInput.body`](https://docs.indeed.com/api/job/objects/UpdateSourcedJobPostingInput). -
Changed the description of input field
UpdateSourcedJobPostingBodyInput.companyNamefrom: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. -
Changed the description of input field
UpdateSourcedJobPostingBodyInput.descriptionfrom: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). -
Changed the description of input field
UpdateSourcedJobPostingBodyInput.descriptionFormattingfrom: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). -
Changed the description of input field
UpdateSourcedJobPostingBodyInput.jobLocationfrom: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. -
Changed the description of input field
UpdateSourcedJobPostingBodyInput.salaryfrom: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. -
Changed the description of input field
UpdateSourcedJobPostingBodyInput.titlefrom: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. -
Object type
UpdateSourcedJobPostingGeneralLocationInputhas description:City, region, postal code, and optional street address. -
Changed the description of input field
UpdateSourcedJobPostingGeneralLocationInput.streetAddressfrom:Street address of the job location.Example: `1600 Pennsylvania Ave`.To:
Street address.Example: `1600 Pennsylvania Ave`. -
Changed the description of type
UpdateSourcedJobPostingInputfrom:Job posting update input.To:
One job posting update. -
Changed the description of input field
UpdateSourcedJobPostingInput.sourcedPostingIdfrom: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`. -
Changed the description of type
UpdateSourcedJobPostingLocationInputfrom:Job location update. Provide one field or the API returns an error.To:
Job location update. Provide one field or the API returns an error. -
Changed the description of input field
UpdateSourcedJobPostingLocationInput.generalfrom:General location input. Accepts values from `cityRegionPostal` to specific addresses.To:
General location, from `cityRegionPostal` to a specific address. -
Changed the description of type
UpdateSourcedJobPostingMetadataInputfrom:Job metadata to update. Provide at least one field.Not atomic. Errors can cause partial updates.To:
Job metadata to update. Not atomic. Errors can cause partial updates. -
Changed the description of input field
UpdateSourcedJobPostingMetadataInput.trackingUrlfrom:Job tracking URL.To:
Tracking URL. -
Changed the description of type
UpdateSourcedJobPostingResultfrom:Return type for each `updateSourcedJobPostings` result.To:
Result for one `updateSourcedJobPostings` operation. -
Changed the description of field
UpdateSourcedJobPostingResult.jobPostingfrom:Updated job posting, or null if the update was not accepted.To:
Updated job posting. Null if the update was not accepted. -
Object type
UpdateSourcedJobPostingSalaryInputhas description:Salary update. -
Changed the description of input field
UpdateSourcedJobPostingSalaryInput.currencyfrom: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. -
Changed the description of input field
UpdateSourcedJobPostingSalaryInput.maximumMinorfrom: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. -
Changed the description of input field
UpdateSourcedJobPostingSalaryInput.minimumMinorfrom: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. -
Changed the description of input field
UpdateSourcedJobPostingSalaryInput.periodfrom: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. -
Changed the description of type
UpdateSourcedJobPostingsInputfrom:`updateSourcedJobPostings` input.To:
Input for `updateSourcedJobPostings`. -
Changed the description of type
UpdateSourcedJobPostingsPayloadfrom:Return type for `updateSourcedJobPostings`.To:
Payload for `updateSourcedJobPostings`. -
Changed the description of field
UpdateSourcedJobPostingsPayload.resultsfrom: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. -
Changed the description of type
WebUrlfrom:Well-formed URL. Specifcation: [RFC 2396/2732](https://en.wikipedia.org/wiki/Uniform_Resource_Identifier)To:
A well-formed URL ([RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986)).