Employer Registration

Employer Registration Public APIs​

API Guidelines​

This Documentation forms an integral part of the Indeed Partner Developer Agreement or Third-Party Developer Agreement (each, hereinafter the "Indeed Partner Developer Agreement"), as applicable, agreed between you and Indeed. By accessing this Indeed API, building the integration or Application, or otherwise using this Indeed API, you agree that: (i) you are granted the license to build the Integration in accordance with the Indeed Partner Developer Agreement and (ii) you accept the Documentation terms and guidelines and (iii) you agree to follow the guidelines contained herein and require any third party platforms for which you build integrations to comply with these guidelines and (iv) you agree not to use this Indeed API for any other purpose or in any other manner than described herein. The Integration is subject to Indeed Verification as described in the Indeed Partner Developer Agreement. If you are unsure which of the below guidelines apply to you, it is your responsibility to reach out to Indeed to confirm.

Employer Registration API Usage Guidelines for ATSes​

• Employer Registration APIs are designed for ATS (applicant tracking system) integrations to enable the Inbound and Outbound Candidate Sync APIs. These APIs enable ATS partners to build integrations that allow their employer clients to efficiently transfer candidate data to Indeed and retrieve candidate data from Indeed.
• ATS partners should ensure that the integration provides clear visibility to employer clients that the integration must be uninstalled from the ATS.
• ATS partners must only request the OAuth scopes required for the Employer Registration when an employer activates the Candidate Sync integration. These scopes are outlined in the ASR API documentation.
• ATS partners should design their integrations to use APIs efficiently and avoid excessive polling that could burden Indeed systems. Follow the recommended best practices outlined in the API documentation.
• ATS partners are responsible for providing first-level support to their employer clients regarding the functionality and usage of the Employer Registration API integration within their ATS. For issues related to the Indeed APIs themselves, ATS partners should follow the designated support channels provided by Indeed.
• Indeed reserves the right to monitor and audit ATS partners' usage of the Employer Registration APIs to ensure compliance with these guidelines and the Indeed Partner Developer Agreement.
• ATS partners are expected to stay updated on any changes or updates to the Employer Registration APIs and these guidelines as communicated by Indeed.
• ATS partners are encouraged to provide Indeed with feedback on their experience with the Employer Registration APIs and suggestions for improvements.
• For any questions or clarifications regarding these guidelines or the Employer Registration APIs, please contact Indeed through the designated partner support channels.
• You agree to inform your End Users that:
  • the use of Indeed Integration is at all times governed by Indeed’s terms of service (https://www.indeed.com/legal) (including section 15 of the Employer terms (Candidate Import), Indeed’s cookie policy (https://hrtechprivacy.com/brands/indeed#Cookies) and privacy policy (https://hrtechprivacy.com/brands/indeed#privacypolicy), and link to those should be provided to your clients (“Indeed Integration Information”);
  • If the End User wishes to deactivate the Indeed Integration, clicking the “remove access” button on Indeed is not sufficient, the End User needs to deactivate the Indeed Integration on the ATS Platform;

Indeed Integration Information shall be provided in the following manner:

• For your End Users that are opted into Indeed Integration by default (if any): you must send a prior notice to all such End Users (via an email, your Platform or website pop-up or similar means), specifying the date of deployment of and/or date of availability of the Indeed Integration or API bundle that allows for the Indeed Integration
• For all your other End Users who must opt into Indeed Integration in order to activate it, within your marketplace page, your implementation guide page or equivalent page, you shall present the Indeed Integration Information on said page to those End Users before such End Users can choose to opt into Indeed Integration (for example, at deployment of the Indeed Integration; when the End User opts into the API bundle that allows for Indeed Integration)