Skip to main content
Rate limits are applied per IntegrationOrganization, not per API client. Your tier is visible via GET /v1/me under capabilities.rateLimitTier.

Tier matrix

  • Read — any GET.
  • WritePOST, PATCH, PUT, DELETE.
  • Webhook management — the /v1/webhooks endpoints specifically.
ENTERPRISE is assigned by agreement; even enterprise tiers have a hard absolute ceiling to protect shared infrastructure.

Response headers

Every response (including 200s) carries rate-limit headers for your category:
  • X-RateLimit-Limit — requests allowed in the current window.
  • X-RateLimit-Remaining — requests still available.
  • X-RateLimit-Reset — Unix timestamp when the window resets.
  • X-RateLimit-Category — which bucket this request counted against.

Rate-limit exceeded → 429

Honor Retry-After. Exponential back-off on top of Retry-After is good defense against stacked bursts, not a replacement.

Client backoff pattern

Idempotent replay is free

A repeat request with the same Idempotency-Key and body returns the cached response. It does not decrement your rate-limit budget. Retrying aggressively after a transient network failure is cheap — you won’t exhaust your quota on the retry.

Webhook deliveries do NOT count

Outbound webhook deliveries are independent of your inbound rate limit. NT24 sending events to your URL does not reduce your budget for calling our API.

Circuit breaker

If we see 10 consecutive 429s from a single API client, we auto-pause that client for 15 minutes and email your organization admin. The pause is per-client, not per-organization — other clients on the same org keep working. Correctly implementing Retry-After and jitter prevents you from hitting the circuit breaker.

Asking for a higher tier

Reach out via our contact page with:
  • Your organizationUuid.
  • Current tier.
  • Expected sustained and peak request rate per category.
  • Business justification.
We adjust tier via capability flag — no code change on your side.

Next

Error reference

Full 429 rate-limited payload.

Idempotency

Free retries via Idempotency-Key.