2026-07-16
GraphQL schema change log: 2026-07-16
📘 Documentation: Updated the GraphQL schema and the GraphQL API Reference with these changes:
-
[log] ✔ Description on type
RichFormattedDescription:SRF Job Description typeHas changed to:
Job description formatted in SRF (Selenium Rich Format). -
[log] ✔ Input field
SourcedJobPostingBodyInput.descriptiondescription changed from:Job description. Maximum 65,000 bytes (1 byte for ASCII, 2-3 bytes for other characters).Must match the details at `SourcedJobPostingMetadataInput.url` and use HTML formatting. 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. 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). -
[log] ✔ Input field
SourcedJobPostingBodyInput.descriptionFormattingdescription changed from:Description format. Use `RICH_FORMATTING` for HTML. HTML has constraints on attributes and element order.To:
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`.