2025-06-15
Updated the GraphQL schema and the GraphQL API Reference with these changes:
Job Sync API
Policy change(1)
Policy change
- Changed the description of
inputfieldSourcedJobPostingMetadataInput.datePublishedDate when this job was[added: , or is to be, ]first published. [added: For some use cases, this could be in the future. If so, this represents when the job will be published and available through <https://indeed.com> or other API endpoints. **DO NOT** set this in the future, unless Indeed has communicated that a clients jobs are eligible for delayed publishing. If Indeed has **NOT** communicated this, and the `publishDate` is in the future, the job will not become available on <https://indeed.com> or other API endpoints. ]**Note:** If your site publishes the publication date, this date must match the date on your site.
Documentation(2)
Documentation
- Changed the description of
inputfieldSourcedJobPostingBodyInput.locationJob location.[added: If creating a job with `seats`, specify the country of all seats ONLY. For jobs with multiple seats in multiple locations, all locations MUST be in the same country.] - Changed the description of
inputfieldSourcedJobPostingMetadataInput.jobPostingIdA unique identifier for the job within the applicant tracking system (ATS). Historically, this value is known as the _reference number_.[added: If defining seats in `SourcedJobPostingBodyInput.seats`, the individual `SourcedJobPostingSeatInput.seatPostingId` values will be each job posts _reference number_. When defining a job with seats, `jobPostingId` is a grouping of one or more seats that become individual job posts in Indeed.]