2026-07-16
Updated the GraphQL schema and the GraphQL API Reference with these changes:
Job Sync API
#Documentation(2)
Documentation
- Changed the description of
inputfieldSourcedJobPostingBodyInput.description[removed: Job ][added: The job ]description[added: shown to job seekers]. Maximum[removed: 65][added: `65],[removed: 000][added: 000`] bytes ([removed: 1][added: `1`] byte for ASCII,[removed: 2-3 ][added: `2` to `3` ]bytes for other characters).[removed: Must ][added: It must ]match the[removed: details ][added: job posted ]at[removed: `SourcedJobPostingMetadataInput][added: [`SourcedJobPostingMetadataInput].[removed: url` and use ][added: url`](/api/job/objects/SourcedJobPostingMetadataInput). The default format is `TEXT`. ]HTML[removed: formatting][added: 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). - Changed the description of
inputfieldSourcedJobPostingBodyInput.descriptionFormatting[removed: Description format][added: Format of the job description].[removed: Use `RICH_FORMATTING` ][added: If the client uses HTML on its job list or job details pages, Indeed generally expects HTML ]for [added: XML and API jobs unless there is a good reason not to include it. Using ]HTML[added: helps the job appear closer to the client version]. [added: Poor formatting can lead to complaints from clients and job seekers. To provide the job description in ]HTML[added: , set this field to `RICH_FORMATTING`. For more information, see [Job description formatting](/job-sync-api/reference/job-description-formatting). HTML ]has[removed: constraints][added: restrictions] on attributes and element order.[added: Default: `TEXT`.]
Job Update API
#Documentation(1)
Documentation
- Changed the description of type
RichFormattedDescription[added: Job description formatted in ]SRF[removed: Job Description type][added: (Selenium Rich Format).]