Namely Rate Limits
Namely publishes exactly one rate limit, and it is unusual in two ways worth recording: it applies to a single endpoint rather than the API as a whole, and exhaustion is signalled with HTTP 406 Not Acceptable rather than the conventional 429 Too Many Requests. No rate-limit response headers are documented, so a client has no runtime signal of remaining budget and must detect exhaustion by pattern-matching a status code that normally means content negotiation failed.
Namely Rate Limits is the machine-readable rate-limit profile for Namely on the APIs.io network, in the API Commons Rate Limits shape.
It captures 1 rate-limit definition.
Limit state is signalled in the documented, observed, and note response headers.
Tagged areas include Human Resources, HCM, Payroll, Employee Data, and Onboarding.
documentedobservednote
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.