Send Candidates

Send Candidates API​

Send 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.

Send Candidates API Usage Guidelines for ATSes​

• Send Candidates API is designed for ATS (Applicant Tracking System) integrations to facilitate the transfer of Candidate data from the ATS to Indeed. This API enables ATS partners to build integrations that allow their End Users to view information about their ATS candidates on Indeed surfaces.

• ATS partners are responsible for using the Send Candidates API to delete candidate from Indeed if the user deletes the candidate or application in the ATS.

• When an End User opts in to the integration, ATS partners are required to send all candidate data that was created in the last 4 years, regardless of the application source, to Indeed. This includes all candidate data elements, along with all candidates that applied on sources other than Indeed (Ex. ATS career site). However ATS partners shall not send an End User's current employees to Indeed. Additionally, if a candidate becomes an employee, that candidate record should be deleted from Indeed.

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

• ATS partners should design their integrations to use APIs efficiently and avoid excessive calls that could burden Indeed systems. Follow the recommended best practices for transfer frequency 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 Send Candidates integration. This may include configuration options within the ATS interface related to data synchronization settings.

• ATS partners must provide a clear and accessible mechanism for their employers to temporarily disable the Send Candidates integration.

• ATS partners must provide a clear and accessible mechanism for their End User to remove the Send Candidates integration. When an End User removes the integration, the Employer Registration API must be called to delete any candidate data that was sent to Indeed.

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

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

• ATS partners are responsible for obtaining all necessary rights and consents from End Users, and providing all necessary information and disclosures to candidates as required under Applicable Data Protection Law to share End Users’ Personal Data with Indeed.

• ATS partners must ensure that only accurate, complete Application data is shared with Indeed. If ATS partner becomes aware of issues related to the data you sent to Indeed through the Indeed Integration, you shall inform Indeed immediately.

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

• If you are providing any documentation or guidance to your End Users regarding the Send 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 Send Candidates API and suggestions for improvements.

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

• You agree to inform your End Users that:

  • the use of the 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)