Nmbrs · Rate Limits

Nmbrs Rate Limits

Nmbrs does not publish fixed numeric per-minute rate limits for its public API. On the REST API, throughput is governed by your subscription product / tier - development (sandbox) subscriptions are more constrained than production subscriptions - and clients should handle throttling responses. The legacy SOAP API operates under a fair-use policy rather than a documented hard limit. Exact numeric caps are not published as of the review date.

Nmbrs Rate Limits is the machine-readable rate-limit profile for Nmbrs on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring requests.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Human Resources, HRIS, Payroll, Rate Limiting, and Quotas.

2 Limits Throttle: 429
Human ResourcesHRISPayrollRate LimitingQuotas

Limits

REST API Requests subscription
requests
tier-based (not published)
Governed by the subscribed product/tier (development vs production); no fixed numeric cap is documented.
SOAP API Requests account
requests
fair-use (not published)
Legacy SOAP v3 operates under a fair-use policy; no strict documented limit. SOAP retiring 2027-03-01.

Policies

Fair Use
The legacy SOAP API is bounded by a fair-use policy rather than a fixed request-rate limit.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Poll Efficiently
With no server-push transport, integrations poll the REST API; use appropriate intervals and filters to avoid unnecessary requests.

Sources