Skip to main content
Rate limiting is partner-scoped: limits are shared across all tenants under the same API key and environment. Each request is classified into 1 of 6 buckets.

​
Buckets

BucketLimitEndpoints
criteria_ai2 req/s + 4 concurrent in-flightPOST /v1/jobs/{jobId}/question-sets, POST /v1/jobs/{jobId}/criteria/generate
scoring_intake_batch1 req/sPOST /v1/jobs/{jobId}/scoring-batches
scoring_intake_single10 req/sPOST /v1/jobs/{jobId}/applications/{applicationId}/scoring-jobs
read_and_ops20 req/sAll other /v1/* endpoints (except analytics and rate-limit status)
analytics20 req/sGET /v1/analytics/*
rate_limit_status2 req/sGET /v1/rate-limit-status
Buckets are isolated: exhausting one doesn’t affect others. The criteria_ai bucket has an extra concurrency cap. At most 4 requests can process simultaneously, returning 429 even if RPS tokens are available.
If you need higher limits, contact us through the Embed Portal.

​
Response headers

All /v1/* responses include: 
X-RateLimit-Bucket: scoring_intake_single
X-RateLimit-Limit: 10
X-RateLimit-Remaining: 8
X-RateLimit-Reset: 1734187201
HeaderDescription
X-RateLimit-BucketWhich bucket the request was classified into
X-RateLimit-LimitMax requests per second for this bucket
X-RateLimit-RemainingRequests remaining in the current window
X-RateLimit-ResetUnix timestamp when the window resets
X-RateLimit-Degraded"true" when rate limiting is in degraded mode

​
Checking status

GET /v1/rate-limit-status returns all buckets at once without consuming tokens from other buckets. Only needs Authorization, not X-Tenant-Id.

​
Handling 429

When rate-limited, the response includes a Retry-After header (seconds to wait).
If you use Idempotency-Key on criteria or library mutations, reuse the same key when retrying after a 429. Rate limiting runs before the idempotency replay layer. Scoring submissions use built-in scoring idempotency instead, so retry the same scoring request directly.
{
  "type": "https://docs.nova.dweet.com/embed-api/errors#rate-limited",
  "code": "RATE_LIMITED",
  "status": 429,
  "message": "Rate limit exceeded. Retry after 2 seconds.",
  "retryable": true,
  "traceId": "5c2f4f5b2c0a4ce0b6a31a1a18f8e9a1"
}
For high-volume backfills, use POST /v1/jobs/{jobId}/scoring-batches with up to 25 applications per request.

​
Degraded mode

If Redis is temporarily unavailable, the system enters degraded mode: requests are allowed through (fail-open), X-RateLimit-Degraded: true is set, and header values are best-effort estimates. Normal limiting resumes automatically when Redis recovers.