429 lookup_limit_reached - NoResponse docs

{
  "type": "https://docs.noresponse.org/problems/lookup-limit-reached",
  "title": "Lookup limit reached",
  "status": 429,
  "detail": "The workspace has made its 50 live console lookups for this UTC day; more run after midnight UTC.",
  "code": "lookup_limit_reached",
  "request_id": "5e8be3a91fde9499f7ce48ae66290895"
}

{
  "type": "https://docs.noresponse.org/problems/lookup-limit-reached",
  "title": "Lookup limit reached",
  "status": 429,
  "detail": "The workspace has made its 50 live console lookups for this UTC day; more run after midnight UTC.",
  "code": "lookup_limit_reached",
  "request_id": "5e8be3a91fde9499f7ce48ae66290895"
}

HTTP 429 Retry after Retry-After

Why

An API key never gets this code, and test lookups do not count. A retry with the same Idempotency-Key does not count again. Retry-After gives the seconds until midnight UTC, at most 3600.

What to do

Run the lookup in the test environment, or wait until midnight UTC. To assess more live identities, send them with an API key. console_lookups on GET /v1/workspaces/{workspace_id}/usage shows how many are left today and when the count resets. This error is temporary. A retry with the same Idempotency-Key is safe.

In the SDKs

The Node and Python SDKs raise RateLimitError. The Go SDK returns *apierrors.RateLimitError, which you match with errors.As.

{
  "type": "https://docs.noresponse.org/problems/lookup-limit-reached",
  "title": "Lookup limit reached",
  "status": 429,
  "detail": "The workspace has made its 50 live console lookups for this UTC day; more run after midnight UTC.",
  "code": "lookup_limit_reached",
  "request_id": "5e8be3a91fde9499f7ce48ae66290895"
}

Every error has this shape. Errors and limits lists every code.