Check Namely's Supported Features documentation to confirm endpoint and field availability before building an integration
domain: developers.namely.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Review the Namely API 'Supported Features' reference alongside the general API introduction
Cross-check the specific objects (e.g. profiles, custom fields, jobs) your integration needs against what's listed as supported
Note any endpoints marked as read-only versus read/write
Build a capability check into your integration setup so unsupported operations fail fast with a clear message
Re-check the Supported Features page periodically via the changelog, since capabilities can change
Known gotchas
Assuming feature parity with other HRIS unified APIs (Merge/Finch) is risky — Namely's native API surface is narrower and documented separately per feature
The changelog is the authoritative source for what changed release to release; third-party unified-API wrappers may lag behind Namely's own documented capabilities
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?