Additional API Terms and Guidelines

Indeed API Data Protection Addendum​

This Data Protection Addendum ("Addendum”) forms part of the Primary Agreement to which it is attached (hereinafter referred together as the “Agreement”) entered into between Indeed and Partner (as defined below) and is effective from the effective date of the Agreement (“Effective Date”). Partner and Indeed are referred to collectively as the "Parties," and individually each as a "Party."

1. Indeed and Partner are engaged through separate agreements or arrangements with an end Client to provide various services to that Client.

2. In the course of providing services, the Parties, acting under Client’s written instruction, may process (by accessing) Client personal data (as defined below) available or hosted through a Partner API or Indeed Applications.

3. The GDPR (as defined below) and other applicable data protection laws require that agreements involving the processing of Personal Data contain certain safeguards. This Addendum is designed to meet these safeguard requirements.

4. The Parties agree that the processing activities are carried out by the Parties as Processor on behalf of the Client pursuant to each Party’s respective Client Agreement and shall comply with the provisions of this Addendum.

Definitions​

Words and expressions used in this Addendum but not defined herein shall have the meanings given to such words and expressions in the GDPR unless otherwise stated herein. Where the Applicable Data Protection Law gives means to such words and expressions that differ from the GDPR, then those meanings in the Applicable Data Protection Law shall apply instead for purposes of compliance with such Applicable Data Protection Law. The following definitions apply to this Addendum unless otherwise specified herein.

“Affiliate” means to any entity that directly or indirectly controls, is controlled by, or is under common control with the Indeed. "Control," for purposes of this definition, means direct or indirect ownership or control of more than 50% of the voting interests of the subject entity.

“Applicable Data Protection Law” means all laws, regulations, and other legal requirements relating to (i) privacy, data security, consumer protection, marketing, promotion, and text messaging, email, and other communications; (ii) the use, collection, retention, storage, security, disclosure, transfer, disposal, and other processing of Personal Data applicable to the processing of Client Personal Data under the Agreement including but not limited to General Data Protection Regulation 2016/679 (“GDPR”), Federal Data Protection Act of 19 June 1992 (Switzerland), UK Data Protection Act 2018 and UK General Data Protection Regulation (UK GDPR), Japanese Act on the Protection of Personal Information (Act No. 57 of 2003 as amended in 2015) and any US state or federal laws or regulations pertaining to the collection, use, disclosure, security or protection of personal data, or to security breach notification, e.g. California Consumer Privacy Act of 2018 (“CCPA”) and California Privacy Rights Act of 2020; the Virginia Consumer Data Protection Act (the “VCDPA”), the Colorado Privacy Act (the “CPA”), the Connecticut Data Protection Act (the “CTDPA”), and/or the Utah Consumer Privacy Act (the “UCPA”) and binding guidance and / or codes of practice issued by the governments, a competent supervisory authority under applicable laws (as defined in the GDPR), or the European Data Protection Board.

“Business Contact Information” means the names, mailing addresses, email addresses, and phone numbers regarding the other Party’s employees, directors, vendors, agents and customers, maintained by a Party for business purposes as further described below.

“Client” (for the purposes of this Addendum) means the Controller and owner of the Client Personal Data (as defined below).

“Client Agreement” means the individual agreements (including data processing agreements) entered into by a) the Client (or Controller) and Partner (or Processor) and b) Client (or Controller) and Indeed (or Processor) defining each parties respective duties and obligations as Controller and Processor.

“Client Personal Data” means either a) Client-owned or controlled personal data provided by or on behalf of Client to Indeed or an Indeed affiliate or subcontractor for processing through use of Indeed services or b) Client-owned or controlled personal data provided by or on behalf of Client to Partner or Partner affiliate or subcontractor for processing under each Party’s respective Client Agreement. Unless prohibited by Applicable Data Protection Laws, Client Personal Data shall not include information or data that is anonymized, aggregated, de-identified and/or compiled on a generic basis and which does not name or identify a specific person.

“Controller, Process (and its derivatives), Processor and Supervisory Authority” have the meanings given to them in the GDPR, except that where Applicable Data Protection Law gives meanings to such words and expressions that differ from the GDPR, then those words and expressions shall have the meanings given to them under Applicable Data Protection Law for purposes of complying with such laws. The term “Processor” includes, without limitation, a “Service Provider” as defined by the CCPA and “business operator handling personal information” as defined by the APPI.

“EU-US Data Privacy Framework (EU-U.S. DPF)” means the EU-U.S. Data Privacy Framework Principles, including the Supplemental Principles and Annex I of the Principles issued by the US Department of Commerce effective July 10, 2023.

“Self certified and participating organization” shall have the same meaning as prescribed under the EU-U.S DPF.

“Indeed” means the Indeed entity/entities/affiliates contracting with the Partner in the context of the Primary Agreement.

“Indeed API” means the Application Programming Interface made available to Partner by Indeed including, without limitation, any updates (as defined in the Agreement).

“Indeed Applications” means any applications developed and provided to Partner by Indeed to communicate or interact with the API, solely for Partner’s use as set forth in the Agreement.

“Partner” means the entity that i) will license the Partner API and its associated tools and documentation for Indeed’s access and use to allow Indeed to build integrations to the Partner API or ii) will be licensed the Indeed API to allow the Partner to build integrations to the Indeed API, as set out in the Agreement .

“Partner API” means means the Application Programming Interface made available to Indeed by Partner including, without limitation, any updates (as defined in the Agreement).

“Personal Data” has the meanings given to them in the GDPR. This definition shall adjust as necessary to include data defined as "Personal Information", "Personally Identifiable Information," and similar terms under Applicable Data Protection Laws.

“Personal Data Breach or information Security Incident” means an actual, confirmed breach of a Party’s technical and organization measures used to protect privacy and security of Client Personal Data that results in the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to such Client Personal Data transmitted, stored or otherwise processed by a Party under the terms of the Agreement or Client Agreement.

“Primary Agreement” means the API license agreement between Indeed and Partner governing access to Indeed APIs or Partner APIs.

“Technical and organizational security measures” means those measures aimed at protecting personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing.

Data Protection Terms​

1. Relationship between the Parties. The Parties to this Addendum acknowledge that they have separate agreements with the Client (who is the Controller) defining their respective duties and obligations as Controller and/or Processor.

2. Compliance with Laws as Processor:

   2.1. Solely to the extent that any Party to this Addendum Processes (by accessing) Client Personal Data under or in connection with the Agreement or Client Agreement, each such Party acknowledges and agrees to comply with its respective obligations as a Processor under Applicable Data Protection Law.

   2.2. If either Party (in its capacity as Processor) is or becomes aware of:

   2.2.1. any reason that would prevent its compliance with Applicable Data Protection Law; or

   2.2.2. any incident of non-compliance with Applicable Data Protection Law in connection with the Processing of Client Personal Data under this Agreement; or

   2.2.3. determines, in its reasonable business judgment, that a Client processing instruction violates any Applicable Data Protection Law (provided that nothing herein shall require the Parties to provide legal or regulatory advice or monitor Applicable Data Protection Laws as they apply to Client), it shall notify the other Party in the most expedient time possible. In such an event, the Parties will work together in good faith to resolve such event in a timely manner. In no event will either Party be required to perform any activity that violates any Applicable Data Protection Law. If the Client requires that a Party or the Parties to follow a processing instruction despite a Party’s notice to the Client that such instruction may violate an Applicable Data Protection Law, the Party shall in such event be responsible for all liability for all claims and damages arising from any continued processing in accordance with such instruction and may (where legally entitled to) recover those costs directly from the Client. In such an event, the Party that continues with the processing shall indemnify and hold the other Party harmless from and against any and all liabilities, costs, expenses, damages and losses arising out of or in connection with such processing.

3. Processing Instructions:

   3.1. The Parties acknowledge and agree that each Party is a Processor of Client Personal Data, and have been engaged by the Client as Processor to process Client Personal Data for the purposes:

   3.1.1. set forth in the Client Agreement and any other written agreement between the Parties, including this Addendum;

   3.1.2. directed, actioned, or otherwise specified to the Parties through the use of any services expressly made subject to this Addendum; and

   3.1.3. disclosing such data as instructed by Client in any other documented instructions to either Party.

   3.2. In all cases, irrespective of whether Applicable Data Protection Law applies to Client Personal Data, the Parties will process Client Personal Data only on Client’s documented instructions and not for any other purpose, unless specifically instructed by Client in writing or otherwise required or authorized by Applicable Data Protection Law.

   3.3. In the event that a Party processes (by accessing Client Personal Data that is outside the scope of Client’s documented Instructions), it is agreed that this Party shall be responsible for all liabilities, claims and damages arising from any continued processing and hold the other Party harmless from and against any and all liabilities, costs, expenses, damages and losses. For avoidance of doubt the limitations of liability contained in the Agreement shall not apply in such an event.

   3.4. Where the GDPR applies to processing of Client Personal Data covered by this Addendum:

   3.4.1. The subject matter of the Parties processing shall be the services the Parties are performing under the Client Agreement.

   3.4.2. The duration of the Parties processing shall be the applicable term of the Client Agreement, in addition to the period of time that either Party’s obligations under this Addendum survive termination of the Client Agreement.

   3.4.3. The nature and purpose of the processing are limited to the services the Parties performs under the Client Agreement, including by way of this Addendum.

   3.3.4. The categories of Personal Data include any Client Personal Data as provided by the Client or otherwise make available to Indeed or Partner through use of Indeed’s platforms.

   3.4.5. The Data Subjects include any individuals whose Personal Data Client provides or otherwise makes available to Indeed or Partner as Client Personal Data.

4. Confidentiality. The Parties personnel, including subcontractors, authorized to process the Client Personal Data shall be subject to confidentiality obligations and/or subject to an appropriate statutory obligation of confidentiality.

5. Data Subject and Supervisory Authority Requests. Taking into account the nature of the processing and the availability of information to it, the Parties shall provide each other with commercially reasonable assistance to fulfill either Party’s obligation to respond to a request from an individual to exercise such individual's rights under Applicable Data Protection Law including any requests from a competent Supervisory Authority. The Parties will not independently respond to such requests from Client’s data subjects, but will refer them to Client, except where required by Applicable Data Protection Law.

6. Security. Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, the Parties will implement appropriate technical and organizational security measures to safeguard Client Personal Data.

7. Information Security Incidents. The Parties shall maintain procedures to detect and respond to Information Security Incidents. If an Information Security Incident occurs which may reasonably compromise the security or privacy of Client Personal Data, the Party will (apart from notifying the Client) if legally permitted and not otherwise prohibited by contract unless required under any Applicable Data Protection Laws also notify the other Party without undue delay. The Parties agree to cooperate with Client (and each other) in investigating the Information Security Incident and provide assistance to Client as required under the contract between the Party and Client, subject to the terms and limitations agreed upon in such contract or required under any Applicable Data Protection Laws.

8. Subprocessors. The Parties acknowledge that it shall adhere to any sub-processing conditions it may have under the agreement with the Client such as entering into a written contract with each such Subprocessor and that remaining fully liable for the performance of each such Subprocessor’s obligations thereunder.

9. Transfers.

   9.1. To the extent that the GDPR applies to the processing of Client Personal Data, the Parties agree that they will not transfer Client Personal Data out of the EEA to a country that has not been identified by the European Commission or a Supervisory Authority under the GDPR as a country that provides an adequate level of data protection except where the Party requiring to undertake the transfer has ensured appropriate safeguards are in place, such as the Standard Contractual Clauses approved by the European Commission unless otherwise required by applicable law.

   9.2. To the extent that the UK Data Protection Act applies, to the processing of Client Personal Data, the Parties agree that they will not transfer Client Personal Data out of the United Kingdom (UK) to a country that has not been identified as a country that provides an adequate level of data protection except where the Party requiring to undertake the transfer has ensured appropriate safeguards are in place, such as the UK Standard Contractual Clauses as amended from time to time by the Information’s Commissioner Office (the “UK SCCs”) unless otherwise required by applicable law.

   9.3. Transfers of EEA/Swiss/UK Data to the US

   9.3.1. Where Personal Data is transferred to the US, transfer from a participating organization as defined under the EU-U.S Data Privacy Framework program (EU-U.S DPF which are detailed here: https://www.dataprivacyframework.gov/), the UK Extension to the EU-U.S. DPF and the Swiss-U.S. Data Privacy Framework program (Swiss-U.S. DPF), shall only take place if the Parties provides for the same level of protection as is available under the EU-U.S. DPF or offers an equivalent independent recourse mechanism.

   9.3.2. Where the Party is not a participating organization as defined under the EU-U.S Data Privacy Framework program, the transfer of Personal Data from the EU/UK/Switzerland to the US shall be done or in accordance with a valid legal mechanism such as the appropriate EU SCC and/or UK Addendum, or a UK International Data Transfer Agreement.

10. Compliance. The Parties shall at all times remain compliant with Applicable Data Protection laws to which they are subject as it relates to the services and where required the Parties shall make available to each other information reasonably necessary to demonstrate compliance with its respective obligations as Processors.

11. Notice. In the event that a Party is required by Applicable Data Protection Law to process Client Personal Data for any other purpose or in any other manner, such Party shall notify the Client of that legal requirement before undertaking such processing, unless the Applicable Data Protection Law prohibits such notification on important grounds of public interest.

12. Termination. Following expiration or termination of the provision of services relating to the processing of Client Personal Data, or at Client’s request, the Parties shall (and shall require that its sub-processors) promptly and securely delete (or return to Client) all Client Personal Data (including existing copies), unless otherwise required or permitted by applicable laws.

13. Costs. Each Party shall be responsible for any and all reasonable costs arising from its provision of assistance in accordance with this Addendum.

14. California Consumer Privacy Act. To the extent that Client Personal Data includes Personal Data of Consumers and is subject to the CCPA, the following additional terms apply to the Processing of such Client Personal Data:

    14.1. The Parties acknowledge and agree that Partner and Indeed both are acting as Service Partners to the Client for purposes of all Processing of such Client Personal Data.

    14.2. The Parties further acknowledges and agrees that it shall (a) not Sell or share such Client Personal Data (as defined by CCPA), (b) not retain, use, or disclose such Client Personal Data for any purpose other than for the Business Purpose(s) specified in accordance with the Agreement, unless permitted by law (c) not retain, use of disclose such Client Personal Data outside of the direct business relationship established by the Agreement and Client Agreement except in all cases as otherwise required by applicable law or permitted by the CCPA ; (d) provide the same level of privacy protection required of such Client by the applicable obligations under CCPA for Client Personal Data ; (e) notify the Client if it can no longer meet its obligations under the CCPA and will work with the Client to take reasonable and appropriate steps to stop and remediate unauthorized use of Client Personal Data.

15. Business Contact Information. Each Party consents to the other Party using its Business Contact Information for contract management, payment processing, service offering, and business development purposes, including business development with partners, and such other purposes as set out in the using party’s Privacy policy (copies of which shall be made available upon request). For such purposes, and notwithstanding anything else set forth in the Addendum with respect to Client Personal Data in general, each Party shall be considered a controller with respect to the other Party’s Business Contact Information and shall be entitled to transfer such information to any country where such Party’s global organization operates.

16. Governing Terms. In the event of an express conflict between the terms of this Addendum and the terms of the Agreement, the terms of this Addendum shall govern solely to the extent of the conflict as necessary to comply with Applicable Data Protection Law. All other terms and conditions within the Agreement remain unchanged and in full force and effect.

17. Changes in Laws. In the event of (i) any newly enacted Applicable Data Protection Law, (ii) any change to an existing Applicable Data Protection Law (including generally-accepted interpretations thereof), (iii) any interpretation of a new or existing Applicable Data Protection Law by Client, or (iv) any material new or emerging cybersecurity threat, which individually or collectively requires a change in the manner by which the Parties are delivering the services to the Client, the parties shall agree upon how the services will be impacted and shall make equitable adjustments to the terms of the Agreement and the services in accordance with the agreed change control procedures.

Authorization​

This Documentation forms an integral part of the Indeed Partner Developer Agreement agreed between you and Indeed. By accessing the Indeed API, building the integration or Application or otherwise using the 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 (ii) you agree to follow the guidelines contained herein and (iv) you agree not to use the 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.

Authorization Guidelines​

• You must register a separate OAuth Application for each Application that you build. You cannot use the same credentials for multiple Applications.

• You must register separate Applications for testing and for production.

• Any Applications that require sensitive and private scopes must be submitted for Indeed review prior to their use in production.

• You must handle authorization for various scopes which means that your Application must handle instances in which a party does not grant all scopes and handle the ones that a party granted. Where possible, you must ask for scopes in context with an option for partial authorization and provide a reason or justification to the party before you request authorization.

You agree to inform your clients that the use of Indeed Integration is at all times governed by Indeed’s terms of service (https://www.indeed.com/legal), 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'').

Indeed Integration Information shall be provided in the following manner:

• For your clients that are opted in to Indeed Integration by default (if any): you must send a prior notice to all such clients (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 clients 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 clients before such clients can choose opt into Indeed Integration (for example, at deployment of the Indeed Integration; when the client opts in to the API bundle that allows for Indeed Integration)

Return to OAuth documentation

Employer Data API Guidelines​

• Identifying Employers:

  • If a client wishes to submit employer details via the Employer Data API, they must first contact Indeed's onboarding partners to get a unique ATS identifier. This ensures their employer data is distinct.

  • While using the Employer Data API, clients must always pair the correct ATS identifier with their internal employer dataset identifier. It's vital that two separate companies never use the same identifier.

  • When utilizing the Job Sync API, clients should consistently use the same combination of ATS identifier and employer identifier. This ensures jobs are correctly linked with their respective employers.

  • It's essential that clients avoid associating jobs with the wrong companies and take active steps to prevent any fraud.

• Data usage:

  • Clients using the API must inform data providers on the ATS side that their information will be shared with Indeed. This data will then be visible to the public on both Indeed and its partner sites.

  • If clients believe data providers might object to how their data is used downstream, they should refrain from sending that data.

  • Clients should never send information if there's a valid concern regarding the illegal use of that content.

• Data validity

  • Clients should ensure that employer information sent through API is relevant and up to date. If employer information is incorrect, misleading or otherwise compromises jobseeker experience, employer and associated jobs can be removed from search results.

  • Clients should be aware that in certain situations, Indeed might display employer information that's different from the client-provided data. This could occur if Indeed believes they have more accurate or trustworthy data about the employer.

Disposition Data​

This Documentation forms an integral part of the Indeed Partner Developer Agreement agreed between you and Indeed. By accessing the Indeed API, building the integration or Application or otherwise using the 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 (iv) you agree not to use the 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.

Disposition Data Guidelines​

• Disposition Data means ApplyID combined with data containing an outcome (aka “status change”) of Platform Partner clients’ interactions with applicants, including but not limited to, whether the applicant was hired or not hired by a client accompanied by a timestamp indicating when the disposition status was updated within the Partner Platform.

• In order for the Disposition Data integration to be functional, you are required to do the following for all eligible jobs within the Partner's clients (Employers) jobs:

  • enable the integration to deliver to Indeed the ApplyID with a single disposition status signal or a sequence of disposition status signals,
  • such signals must be accompanied by a timestamp indicating when the disposition status was updated within the Partner Platform, for all eligible jobs within the Partner's clients (Employers) jobs,
  • the signals must be delivered to Indeed daily, at a minimum.

• A Disposition Data integration will not be considered approved if it fails to include the ApplyID or if it contains Personal Data excluding the ApplyID.

You agree to inform your clients that they will be opted-in to share Disposition Data with Indeed, via a prior notice to all such clients (through 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. In such notice, you must include information that the use of Indeed Integration is at all times governed by Indeed’s terms of service (https://www.indeed.com/legal), 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''). You must specifically share that Disposition Data will be transferred to Indeed as data controller in accordance with Indeed’s privacy policy (https://hrtechprivacy.com/brands/indeed#privacypolicy).

Return to the Disposition Data CSV guide

Disposition Sync API​

This Documentation forms an integral part of the Indeed Partner Developer Agreement agreed between you and Indeed. By accessing the Indeed API, building the integration or Application or otherwise using the 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 (iv) you agree not to use the 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.

Disposition Sync API Guidelines​

• Disposition Data contains an outcome (aka “status change”) of Platform Partner clients’ interactions with applicants, including but not limited to, whether the applicant was hired or not hired by a client accompanied by application identifier (to uniquely identify an application), and a timestamp indicating when the disposition status was updated within the Partner Platform.

• For the Disposition Data integration to be functional, you are required to do the following for all eligible jobs within the Partner's clients (Employers) jobs:

  Enable the integration to deliver to Indeed the unique application identifier(s) with a single disposition status signal or a sequence of disposition status signals.

  • Such signals must be accompanied by a timestamp indicating when the disposition status was updated within the Partner Platform, for all eligible jobs within the Partner's clients (Employers) jobs.

  • The signals must contain the original disposition status as shown in the Partner’s system, and the corresponding Indeed’s standard disposition status mapped from this original disposition status.

  • At a minimum, the signals must be delivered to Indeed daily.

You agree to inform your clients that they will be opted-in to share Disposition Data with Indeed, through a prior notice to all such clients (through an email, your Platform, 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. In such notice, you must include information that the use of Indeed Integration is at all times governed by Indeed’s terms of service (https://www.indeed.com/legal), Indeed’s cookie policy (https://hrtechprivacy.com/brands/indeed#Cookies) and privacy policy (https://hrtechprivacy.com/brands/indeed#privacypolicy), and links to those should be provided to your clients (“Indeed Integration Information''). You must specifically share that Disposition Data will be transferred to Indeed as data controller in accordance with Indeed’s privacy policy (https://hrtechprivacy.com/brands/indeed#privacypolicy).

A Disposition Data integration must provide an explicit option to opt-out of sending Disposition Data to Indeed (this option to opt-out must be made available for your clients at any time by either (i) providing your clients with your company contact email or (ii) providing an opt-out functionality within your Platform. (NOTE such clients shall NOT under any circumstances be instructed to contact Indeed to opt-out).

Indeed Apply Sync​

This Documentation forms an integral part of the Indeed Partner Developer Agreement agreed between you and Indeed. By accessing the Indeed API, building the integration or Application or otherwise using the 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 (ii) you agree to follow the guidelines contained herein and (iv) you agree not to use the 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.

Indeed Apply Sync Guidelines​

• Indeed Apply can be provided by an ATS (Applicant Tracking System (ATS) Guidelines), an Employer directly, or an Indeed approved 3rd party designated by the employer.

  • 3rd parties must be vetted and approved by Indeed prior to building an integration on behalf of a Direct Employer.

• Indeed defines an ATS as an applicant tracking system that focuses on hosting employer career pages and applicant tracking, sorting, screening, and reporting on applications/hires for their clients. The ATS is the system of record for all jobs data, recruiting processes, and dispositions.

• Screener questions must be available via the Indeed Apply integration and if you are a US based ATS or are an ATS that has End Users that advertise jobs based in the US or an approved 3rd party builder that meets one of the aforementioned criteria, you must also provide EEO functionality if applicable.

• Screener questions must be available via the Indeed Apply integration and if US based ATS or approved 3rd party, you must also provide EEO capabilities if applicable.

• By using the Indeed Apply API in connection with your Job Listings, you agree to require your End Users to agree that they will not require or otherwise burden a Job Seeker to submit a duplicate application through other means if that Job Seeker already applied to their Job Listing using Indeed Apply.

• You further agree to require your End Users to accurately describe to a Job Seeker what information and data your End Users collect from and about that Job Seeker when they apply to your End User’s job using Indeed Apply, including how you handle and share such information and data. You also agree to honor a Job Seeker request for their information and data that you collect in connection with any API.

• You must replicate into Indeed Platform the Employer screener/application questions present in your Platform. Screener/application questions provided to Indeed via an URL shall be available under that URL at all times.

• You shall not configure any parts of the application experience that aren't clearly provided by Indeed as configurable.

• You shall not filter or alter applications submitted by Jobseekers.

• You shall immediately notify Indeed in writing to marketplacesupport@indeed.com of any applications that cannot be processed by your Platform.

• You shall provide an unrestricted and unmodified test Employer account(s) to Indeed and Indeed reserves the right to test Jobseeker application experience by, among other actions, posting test Job Listings. Indeed is not obliged to perform this test.

• If you are provided with a URL to specify additional steps required from Jobseekers to apply to Job Listings (such as FinishAppUrl) you shall configure and enable such URL and ensure its appropriate availability.

• You must inform Indeed of any domain changes to your career pages (pages where the job advertisements are hosted) that would impact the Indeed Apply HTML, at least 30 days prior to implementing such changes.

You agree to inform your clients that the use of Indeed Integration is at all times governed by Indeed’s terms of service (https://www.indeed.com/legal), 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”).

Indeed Integration Information shall be provided in the following manner:

• For your clients that are opted in to Indeed Integration by default (if any): you must send a prior notice to all such clients (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 clients 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 clients before such clients can choose opt into Indeed Integration (for example, at deployment of the Indeed Integration; when the client opts in to the API bundle that allows for Indeed Integration)

In addition, you shall include the following in the Indeed Integration Information on Indeed Apply Integration:

• How Indeed Apply works, as provided by Indeed;

• That clients’ Job Listings will now be included in a comprehensive feed delivered to the Indeed Platform, which includes Indeed.com together with the global domains in other jurisdictions and all websites owned by Indeed and its Affiliates which syndicates Job Listings, including but not limited to SimplyHired, Resume.com and Glassdoor;

• That applicants will now be able to apply to clients’ Job Listings on Indeed using the Indeed Apply functionality;

• That applicants will now apply to clients’ Job Listings on Indeed and the resulting application will be ingested by your, and applicants will not be directed to clients’ career pages to apply for a job;

• They have an explicit option to opt-out of the Integration and/or Indeed Apply feature (this option to opt-out must be made available for your clients at any time by either (i) providing your clients with your company contact email or (ii) providing an opt out functionality within your Platform. (NOTE such clients shall NOT under any circumstances be instructed to contact Indeed to opt-out).

Apply with Indeed​

This Documentation forms an integral part of the Indeed Partner Developer Agreement agreed between you and Indeed. By accessing the Indeed API, building the integration or Application or otherwise using the 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 (iv) you agree not to use the 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.

Guidelines​

• For Apply with Indeed to be fully functional, you are required to also integrate with the following Indeed APIs/Services and comply with the Documentation for those APIs/Services:

  • Disposition Sync API
  • Indeed Apply Sync

• You should ensure that the Apply with Indeed button has a design (color, style, text etc.) that is consistent with the 'Button design' specifications described in the Apply with Indeed integration guide.

• You are required to automatically opt-in Apply with Indeed for all the jobs enabled with Indeed Apply for all of your End Users.

You agree to inform your End Users that all jobs enabled with Indeed Apply will automatically be opted-in with Apply with Indeed, by providing prior notice to all such End Users (through an email, your Platform, 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. In such notice, you must include information that the use of Indeed Integration is at all times governed by Indeeds terms of service (https://www.indeed.com/legal), Indeeds cookie policy (https://hrtechprivacy.com/brands/indeed#Cookies) and privacy policy (https://hrtechprivacy.com/brands/indeed#privacypolicy), and links to those should be provided to your End Users (“Indeed Integration Information'').

The Apply with Indeed functionality must provide an explicit option to opt out. This option to opt-out must be made available for your End Users at any time by either (i) providing your End Users with your company contact email or (ii) providing an opt-out functionality within your Platform. (NOTE: End Users shall NOT under any circumstances be instructed to contact Indeed to opt out).

• You are responsible for opting-out any of your End Users of Apply with Indeed upon their request. This can be done with or without opting-out the job from having Indeed Apply enabled. In case any engineering support from Indeed is required for the above, you should inform Indeed as early as possible.
• You agree to follow the integration technical instructions shared with you. You are responsible for ensuring that Apply with Integration is working effectively and operational issues are being resolved so as not to block the Job Seeker.
• If Indeed notices operational or technical issues with the Apply with Indeed integration on your Platform, Indeed will disable the API on your Platform and display an appropriate error message. The integration will be kept disabled until the operational or technical issues are resolved.
• In case Indeed returns such an error message, you agree to make reasonable efforts to redress the degradation or outage so that the Job Seeker experience is not compromised, including by following the troubleshooting and error handling guidelines shared with you.

Indeed Interview API​

This Documentation forms an integral part of the Indeed Partner Developer Agreement agreed between you and Indeed. By accessing the Indeed API, building the integration or Application or otherwise using the 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 (ii) you agree to follow the guidelines contained herein and (iv) you agree not to use the 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.

Indeed Interview API Guidelines​

You agree to place a button in your user interface that will allow your clients (Employers) to create an interview with Indeed Platform. The button will meet the specifications provided by Indeed.

You agree to accurately describe to a Jobseeker:

• What information and data you collect from and about that Jobseeker and how that data is shared with Indeed when such Jobseeker are scheduled for an interview, including how you handle and share such information and data.

• You also agree to honor a Jobseeker request for their information and data that you collect in connection with any API.

• You agree to provide ATS Name, Employer Name, Job Identifiers, and Interviewee email address, via this API, when that data is available to you.

You acknowledge that your and your clients’ use of the Indeed Integration is at all times governed by Indeed’s terms of service (https://www.indeed.com/legal), Indeed’s cookie policy (https://hrtechprivacy.com/brands/indeed#Cookies) and privacy policy including data protection language (https://hrtechprivacy.com/brands/indeed#privacypolicy) and Indeed will require your clients’ to agree to those terms. Any information displayed by you on your Portal in relation to this Indeed Integration should include the reference to Indeed’s terms of service (https://www.indeed.com/legal), Indeed’s cookie policy (https://hrtechprivacy.com/brands/indeed#Cookies) and privacy policy including data protection language (https://hrtechprivacy.com/brands/indeed#privacypolicy) and link to those should be provided to your clients ("Indeed Integration Information").

Return to Indeed Interview API documentation

Job Sync API​

This Documentation forms an integral part of the Indeed Partner Developer Agreement agreed between you and Indeed. By accessing the Indeed API, building the integration or Application or otherwise using the 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 (iv) you agree not to use the Indeed API for any other purpose or in any other manner than described herein. The Integration is subject to Indeed ld Verification as described in the Indeed Partner Developer Agreement.

Job Sync API Guidelines​

• You must provide a comprehensive list of all jobs for all your clients via the API.

• You should not include content from any other products that are not your ATS product.

  • You should only include content from paid clients; and

  • You agree Indeed does not allow content from clients that are using a free-trial period

  • Indeed will not accept any job listing from ATSs that are in Beta.

• Indeed requires that you provide accurate metadata in the appropriate API fields to separate out staffing/recruiting content.

• API integrations are intended to be near real-time. When you create, update, and expire jobs, ensure you send changes immediately when the changes go live on your clients’ career sites. If a job changes on the client’s website and Indeed doesn’t receive an update within 15 minutes, it may now result in lowered visibility for that job.

• All your job data in the API must match the job data on the individual clients’ career sites.

• The job URL you transmit to the Job Sync API must link to a landing page that includes a job description that matches the information transmitted to the Job Sync API.

• Your clients cannot use a different ATS on their company website. For example, if Indeed receives a job listing from an ATS partner and discovers one of their clients, Company X, is using a different ATS on companyx.com, then Company X cannot be included in the ATS’s job data.

• You are required to provide the email address for each client (this data is subject to our Privacy Policy).

• You agree that test jobs are not allowed on Indeed.

  • Except in the course of your test phase during onboarding; however these jobs may not be provided in production data.

• All your job postings are held to Indeed policies and guidelines.

  • Job Posting Standards

  • General Product Policies

  • All other Policies

• You must only submit jobs for which your software is the source of truth, not on behalf of other job boards or applicant tracking systems.

• If your clients are required to include certain information (such as the job type, responsibilities and salary) in their Job Listings under the applicable laws, you shall ensure that your ATS allows your clients to do so in its job posting function and provides the information to Indeed via the API. You shall inform your clients that they need to promptly inform Indeed of any change in their Job Listings by updating the Job Listings on your ATS or otherwise taking such methods as designated by Indeed. If Indeed deems it necessary to conduct an investigation to confirm the accuracy and legality of the Job Listings, you shall cooperate on the investigation and submit such materials as Indeed determines necessary.

• Indeed may reformat some text fields, such as the job title or description, to improve compatibility. The most common examples of these changes are:

  • Removing HTML or what appears to be HTML

  • Converting some full-width symbols to half-width

  • Removing some symbols, such as the characters on Unicode/Character reference/2000-2FFF

  • Removing trailing or leading asterisks

  • Removing double spaces

• You further agree job postings that do not meet Indeed standards may be subject to review and require additional information from the hiring company. Job posting that prove misleading, compromise the Job Seeker experience or those which we are not convinced represent a “real” job may be removed from search results altogether. Please note: Indeed may reject or remove any job listing and may disable any Company's account, for any or no reason. We cannot give every reason why a job listing or a company may be removed, and we always retain the right to remove any job listing, organic or sponsored, if we feel it is in our interest or our users’ interest.

You agree to inform your clients that the use of Indeed Integration is at all times governed by Indeed’s terms of service (https://www.indeed.com/legal), 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'').

In addition you agree to the additional API terms and guidelines for Indeed Apply and, unless you are based in Japan, the additional API terms and guidelines for Disposition Sync as these integrations are included in the Job Sync API:

• For the Indeed Apply and (unless you are based in Japan) Disposition Sync component of the Job Sync integration the following additional terms apply:

  • https://docs.indeed.com/legal-terms/additional-api-terms-and-guidelines#indeed-apply-sync

  • https://docs.indeed.com/legal-terms/additional-api-terms-and-guidelines#disposition-sync

  • (Data Protection Addendum) https://docs.indeed.com/legal-terms/additional-api-terms-and-guidelines#indeed-api-data-protection-addendum

Return to Job Sync API documentation

Seamless Account Creation API​

1. Permitted use of and access to the Seamless Account Creation (“SAC”) API, is conditional on:

i. The Partner receiving a job feed from Indeed as permitted under a separate written agreement;

ii. The Partner not using the SAC API for any jobs acquired through means other than directly from Indeed; and/or

iii.In circumstances where the Partner is accessing the API without a job feed from Indeed, it is only for discovery and testing purposes and as expressly consented to by Indeed.

2. Indeed reserves the right to revoke access to or use of the API at any time in its sole discretion.
3. Partner will notify all End Users that by accessing or using the API, the End User is explicitly granting Indeed consent to use the information it has stored with the Partner and for that information to be shared with Indeed.
4. Where the Partner exclusively maintains End User consent records, the Partner will deliver such records to Indeed upon termination or expiration of the API Agreement.

Return to Seamless Account Creation API documentation