Sign a Developer Agreement with Indeed before beginning development; integration requires a formal partner relationship — contact Indeed's developer team to initiate this process
Create and host an XML job feed that conforms to Indeed's Job Sync XML feed specification (documented at docs.indeed.com/indeed-apply/xml-feed); the feed must include all active jobs and Indeed does not support partial opt-in feeds
Embed the Indeed Apply button on job posting pages by including the Indeed Apply JavaScript snippet with your employer account ID and the apply URL configured to point to your ATS ingestion endpoint
Configure your ATS ingestion endpoint to accept Indeed Apply POST payloads, which contain applicant PII, resume, screener question answers (schema version denoted as 1.X in the Application payload), and an Indeed-issued applicant token
Return HTTP 200 with a JSON body containing an applicationId (your ATS's internal ID for the application) to acknowledge receipt; Indeed uses this to confirm delivery
Test the integration using Indeed's sandbox environment before going live; validate that screener question schema versions 1.1 and later (introduced January 2024) are handled correctly
Known gotchas
Indeed does not accept incomplete XML feeds — every active job from the employer must be included; omitting jobs from the feed will cause them to be removed from Indeed
Indeed has been phasing out XML-only feed approaches in favor of API-based job submission; confirm the current preferred integration path with your Indeed partner contact as the landscape was evolving as of 2024-2025
The Developer Agreement must be signed before API credentials and sandbox access are provisioned; build this lead time (potentially weeks) into your project plan
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp