Distribute a job posting via the Appcast programmatic job advertising XML feed
domain: recruiting · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Get onboarded with an Appcast account manager/partner contact to receive your Appcast Client ID and set up the integration's three connection points: job feed, apply attribution, and source attribution
Provide an XML job feed Appcast can ingest — most major ATSs (Greenhouse, iCIMS, Lever, Workday, etc.) have a pre-built native or certified feed export; otherwise host your own feed at a stable HTTPS URL and share it with your Appcast contact
Ensure each job entry includes the fields Appcast expects for ingestion and matching (title, description, location, apply URL, date posted, company, reference/job ID, category)
Deploy Appcast's apply-attribution tracking script/pixel on the actual completed-application confirmation step so finished applications are attributed to Appcast-driven traffic
Set 'Appcast' as a recognized application source within your ATS so incoming applications are tagged correctly for source-of-hire reporting
Monitor the Appcast dashboard for feed-ingestion and attribution errors, since misconfiguration silently undercounts conversions rather than throwing visible errors
Known gotchas
Appcast is a programmatic job-ad exchange built on XML feed ingestion plus tracking pixels/scripts, not a general request/response REST API called per job posting — don't design around typical CRUD endpoints
Feed URLs must be served over HTTPS; partner integration guides explicitly note plaintext HTTP feeds are not accepted
Apply-attribution tracking must sit on the true completed-application step, not just the apply-click — misplacement breaks conversion tracking even though feed ingestion itself looks fine
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?