Retrieve Candidates

Retrieve Candidates API​

Retrieve Candidates 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.

Retrieve Candidates API Usage Guidelines for ATSes​

• Retrieve Candidates API is designed for ATS (applicant tracking system) integrations to facilitate the retrieval of Candidate data from Indeed to the ATS. These APIs enable ATS partners to build integrations that allow their End Users to efficiently access and manage candidate data sourced through Indeed products directly within their ATS.

• ATS partners must utilize the provided API endpoints to pull Candidate data from Indeed. These APIs are not designed for Indeed to push data to the ATS. Your integration must be built to actively request and retrieve data as needed based on the API specifications.

• ATS partners are responsible for securely storing and processing the Candidate data retrieved from Indeed. When handling this data within your ATS, you must adhere to all applicable data privacy regulations and security best practices. This includes, but is not limited to, implementing appropriate access controls, data encryption, and data retention policies.

• ATS partners are required to acknowledge the successful receipt and processing of data pulled from the Retrieve Candidates API. This acknowledgment mechanism, as defined in the API documentation, is essential for Indeed to track data transfer status and provide End Users with visibility into data synchronization. ATS partners are responsible for promptly notifying Indeed of any issues they identify with the receipt and processing of data pulled from the Retrieve Candidates API.

• ATS partners should ensure that the integration provides clear visibility to End Users regarding the data being synced from Indeed via the Retrieve Candidates API. This includes communicating the types of data being retrieved, the frequency of synchronization (if applicable), and the status of data transfers.

• ATS partners must not alter or filter the Candidate data retrieved from Indeed in a way that misrepresents the original data or its source. The data should be presented within the ATS integration in a manner that accurately reflects the information provided by Indeed.

• ATS partners should design their integrations to use APIs efficiently and avoid excessive polling that could burden Indeed systems. Follow the recommended best practices for polling frequency and data retrieval strategies outlined in the API documentation.

• ATS partners must provide a clear and accessible mechanism for their End Users to understand and, if necessary, manage their Retrieve Candidates integration. This may include configuration options within the ATS interface related to data synchronization settings.

• ATS partners are responsible for providing first-level support to their End Users regarding the functionality and usage of the Retrieve Candidates integration within their ATS. For issues related to the Indeed APIs themselves, ATS partners should follow the designated support channels provided by Indeed.

• ATS partners must not use the Retrieve Candidates API for any purpose other than facilitating the intended integration of Candidate data from Indeed to their ATS for the benefit of their End Users. Any misuse or unauthorized use of these APIs is a violation of the Indeed Partner Developer Agreement.

• ATS partners are expected to stay updated on any changes or updates to the Retrieve Candidates API and these guidelines as communicated by Indeed.

• If you are providing any documentation or guidance to your End Users regarding the Retrieve Candidates integration, you must ensure it is consistent with these guidelines and accurately reflects the functionality and purpose of the integration.

• ATS partners are encouraged to provide Indeed with feedback on their experience with the Retrieve Candidates API and suggestions for improvements.

• For any questions or clarifications regarding these guidelines or the Retrieve Candidates API, please contact Indeed through the designated partner support channels.

• ATS partners should ensure that the integration provides clear visibility to End Users that a Smart Sourcing professional subscription is required to transfer prospects to the ATS.

• 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)