August 4, 2025

 

Release notes: August 4, 2025

Authorization

• Updated and expanded Japanese documentation for the 2-legged OAuth authorization process.
  • Improved step-by-step guidance and updated terminology for getting access tokens and employer-specific tokens.
  • Enhanced tables and examples for request headers and body parameters, making it easier to implement the OAuth flow.
  • Added detailed guidance on building employer selection screens.

Employer Data API

• To clarify that the maximum number of SUIDs allowed is 3, updated the sectorSUIDs field description in CountrySpecificEmployerAttributesInput.
  • This change helps partners understand the field's constraints when integrating with the Employer Data API.

Get started

• Added Ruby on Rails client guidance to the GraphQL clients best practices. This guidance ensures that operation names are used correctly when invoking GraphQL queries and mutations in Ruby on Rails by storing queries in constants.

GraphQL Schema

• Updated GraphQL API reference documentation to reflect recent schema changes:
  • Added documentation for new input fields such as applicationVersionStatusTypes, indeedRegistrationIds, and applicationVersionIds in filter inputs for candidate application status queries.
  • Documented the removal of deprecated types and fields, including AtsSyncCandidateSyncApplicationFindLatestStatusesPayload, AtsSyncCandidateSyncApplicationFindStatusesPayload, and versionIds input field.
  • Added and updated descriptions for relay-style pagination fields and arguments, including edges, pageInfo, after, before, first, and last on relevant queries.
  • Clarified the use of filter fields for application status queries, including applications and indeedRegistrationIds.
  • Improved field and argument descriptions for better clarity and accuracy, including updates to FindEmployerJobsPartnerFilterInput and related fields.
• Added detailed documentation for new GraphQL types and fields supporting ATS Candidate Sync integration. The updates include:
  • Descriptions for AtsSyncCandidateSyncApplicantDetailsInput fields such as attachments, awards, certifications, education, languageProficiencies, military, skills, workExperience, and more.
  • Field-level documentation for file attachment handling, including checksumMd5, contentLength, contentType, fileName, fileType, and url for presigned upload URLs.
  • Guidance on providing accurate applicant address information for geolocation purposes.
• Improved GraphQL API reference for screener question input fields.
  • Updated descriptions for fields, such as condition, required, and format, in various question input types, such as DateQuestionInput, DecimalTextQuestionInput, and DemographicQuestionsBodyInput.
  • Clarified requirements and behavior for conditional questions, required/optional fields, date formatting, and answer handling.
  • Aligned documentation language for consistency and improved developer understanding.
• To improve clarity and consistency, updated descriptions for the following input objects and fields in the Occupational Metadata API reference:
  • RelatedTaxonomyConceptsInput: Clarified the relationship description for the relatedTaxonomyConcepts query.
  • TaxonomyConceptsInput: Refined the explanation for filters in the taxonomyConcepts query.
  • TaxonomyConceptsInput.global: Included concepts not tied to specific country or language codes.
  • TaxonomyConcept.customClasses: Improved description for custom class membership.
  • classifyOccupationsForJobDetails: Enhanced guidance on providing input for higher-quality results.

Indeed Apply

• Added documentation for creating job postings with Indeed Apply screener questions using the Job Sync API.
  • Added guidance on how to include screener questions when creating or upserting job postings through the API. See Job Sync API guide and Screener questions for details.
  • Clarified requirements and updated examples for the jobsIngest.createSourcedJobPostings mutation, including how to specify screener questions in the request payload.
  • Improved related documentation including integration guidance and common issues.
• Updated the Trusted root SSL certificates documentation for Indeed Apply. To ensure their SSL certificates are supported, partners who integrate with Indeed Apply should review this list, which reflects the current set of root SSL certificates trusted by Indeed Apply.
• Added documentation for firstName and lastName fields in the applicant object for Indeed Apply application data.
  • These fields are available when indeed-apply-name is set to firstlastname.
  • For details and examples, see the updated applicant object fields table.

Job Sync API

• Deprecated the admin1Code, admin2Code, admin3Code, and admin4Code fields in the Job Sync API guide and Job Update API guide.

• Updated the Job Sync API guide to fix broken images and add missing details about job visibility.

  • Images in the job status table now render correctly for all users.
  • Expanded the description on job visibility, including adding conditions for when jobs are searchable, require sponsorship, or are not available in search results.
  • Clarified use of isRejected, isMissingRequiredSponsorship, and isSponsorshipRequired fields.

• Described the lifecycleStatus field in the globalStatus object in both the Job Update API guide and the Job Sync API guide.

  • The new lifecycleStatus field describes the processing state of a job, with possible values: PENDING (job is being processed), ACTIVE (job is processed and unexpired), and INACTIVE (job is no longer active or is expired).
  • To show the correct placement of lifecycleStatus within jobPost.status.globalStatus, updated examples and schema references.

• Added and updated Japanese translations for the Job Sync API and Job Update API. These translations include:

  • Expanded Japanese-language FAQ coverage for the Job Sync API FAQs, with comprehensive answers for Japanese partners.
  • New and improved Japanese content for Job Sync API operations and guidance, such as job posting details and expiration handling. These updates help Japanese-speaking developers and partners better understand and implement Job Sync and Job Update API integrations.

Publisher JS Plugin

• Consolidated the English and Japanese Publisher JS Plugin documentation into one main page for both languages. This update improves navigation and ensures consistency across English and Japanese documentation for the plugin.

SCIM API

• Added documentation for the SCIM API, which enables third-party systems to synchronize user directories with Indeed PLUS:
  • Comprehensive SCIM API guide and SCIM API schemas
  • SCIM API reference for technical integration details

Support

• Clarified requirements for maintaining tiered status in the Partner Program on Support:
  • Added details about the risk of losing tiered status for partners placed on Feed Source Approval (FSA).
  • Updated the support form link for partners without a dedicated partner manager.
  • Replaced the Partner Program requirements link with the latest 2025 booklet.

Other

• To improve accessibility and usability, added captions to images and tables across multiple documentation pages.
• Added descriptive captions to tables to improve accessibility and usability.

 

Was this page helpful?