Rate Limits

Retrieve the current request and quota limits for your account.

GET/search/v2/limits

Related NOSIBLE resources

research & data

Inspect the Search data dictionary or read NOSIBLE research for implementation context and methods.

Authorizations

apiKey

Api-Keystringrequiredheader

Your NOSIBLE API key.

Example: nos_sk_...

How to use this endpoint

guidance

Call Rate Limits before building a scheduler or increasing concurrency. Treat the returned limits as account configuration, not a guarantee that every request will complete within the same latency budget. The route returns one entry per configured quota window.

Response body

application/json

These are the fields you can build against. Nested names use dot notation; optional sections are called out in their descriptions.

api_key_idstring

Identifier for the API key used for the request.

Example: key_01J...

subscription_idstring

Subscription associated with the API key.

Example: sub_01J...

limitsobject[]

Current quota windows and remaining capacity.

Example: [{ name, query_type, duration_seconds, limit, remaining, period_start, period_end }]

limits[].namestring

Human-readable quota name.

Example: Fast Search

limits[].query_typestring

Operation family governed by the quota.

Example: fast

limits[].duration_secondsinteger

Length of the quota window in seconds.

Example: 60

limits[].duration_stringstring

Human-readable quota duration.

Example: 1 minute

limits[].limitinteger

Maximum requests allowed in the current window.

Example: 120

limits[].limitedboolean

Whether this quota is currently enforced.

Example: true

limits[].remaininginteger

Requests remaining in the current window.

Example: 117

limits[].period_startdatetime

Start of the current quota window.

Example: 2026-07-21T10:00:00Z

limits[].period_enddatetime

End of the current quota window.

Example: 2026-07-21T10:01:00Z

Responses and errors

HTTP

200Request succeeded. The response body is shown in the panel on the right.

400invalid_request — The request is syntactically valid JSON but a value, date, filter, or combination of fields is invalid.

401unauthorized — The required API key or Bearer credential is missing or invalid.

422validation_error — The request shape is understood but one or more values fail validation.

429rate_limited — The request exceeded the account or public-window rate limit. Respect Retry-After when supplied.

502upstream_error — An upstream retrieval service failed while processing the request.

504upstream_timeout — An upstream retrieval service did not respond within the request timeout.