Handle the legacy /offers endpoint in Recruitee's (Tellent) API when building or migrating an integration
domain: docs.recruitee.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Note that the /offers endpoint is explicitly labeled a legacy endpoint in the API reference
Follow the documentation's link to the support article describing the newer parameter set before building new integrations
Treat the legacy response as returning the company's job postings in the old shape only, without assuming new fields will appear
Authenticate as documented for the API (OAuth2/Bearer credentials)
Plan a migration path toward the documented newer parameters rather than assuming indefinite long-term support
Known gotchas
No public sunset or deprecation date is stated in the docs for /offers — it is only marked legacy with a newer parameter set available; do not assume or invent a retirement date
Migration guidance lives in a support-center article rather than a versioned API changelog entry
The product has rebranded to Tellent while API and docs hostnames remain on recruitee.com, which can cause confusion when searching for current guidance
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?