Publish a Recruitee XML job feed to external job board partners
domain: docs.recruitee.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the jobs to expose are published in Recruitee; only published offers appear in the XML feed, and status changes take effect immediately.
Share the feed URL with job board partners using the pattern https://{yourcompany}.recruitee.com/api/feeds/offers.xml, replacing {yourcompany} with your Recruitee careers-site subdomain.
Instruct the job board to parse the XML feed; each job appears as a <job> element with a <locations> node containing one or more <location> child nodes — the first location's fields (city, country, postal_code, etc.) are also mirrored at the top level for boards that expect flat structure.
If the job board requires credentials (e.g., a board-specific username/password), configure those credentials in Recruitee's job board settings; the feed will then include a <credentials> node in the relevant job entries.
Monitor the feed by fetching the URL directly and verifying that new or updated jobs appear and that unpublished jobs are absent.
Known gotchas
The XML feed URL requires no authentication token from the consumer — it is a public URL scoped to your subdomain; treat the URL itself as semi-sensitive and share it only with trusted partners.
Recruitee webhook rate limits for trial accounts are capped at 100 requests per minute for the ATS API; the XML feed itself is not subject to the same per-minute cap, but excessive polling can be throttled.
The feed only reflects currently published jobs; jobs moved to archived or draft status disappear from the feed immediately, which may cause job boards that cache feed data to show stale listings until their next sync cycle.
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?