Help centre ↗
← All help articles
API & ACCOUNT

API access, errors and rate limits

Resolve common authentication, request, coverage and rate-limit problems.

401 Unauthorized

Send Authorization: Bearer followed by a valid API access token or an authorized legacy operator key. An account session or a token issued for a different audience is not necessarily an API access token. For OAuth, use the API resource https://api.findata.com in both authorization and token requests, and check expiration and the client’s redirect URI.

400, 404 and 409

A 400 indicates invalid input such as an unsupported date, metric or parameter. Dates use YYYY-MM-DD. A 404 may mean the company or metric is not present in the imported index. A 409 means a ticker resolves to multiple companies; use the intended CIK instead.

429 and temporary errors

During the current free launch, OAuth users are limited to 20 requests per minute per user at each Cloudflare location; the legacy operator-key limit is 60 per minute per connecting IP. Limits are approximate and location-specific, not a global quota. A 429 includes Retry-After: 60; wait and retry with backoff.

A 422 from the aligned series route means too many candidate facts; narrow the date range. A 500 or 503 can indicate a temporary service or configuration problem. If it persists, contact hello@findata.com with the endpoint, timestamp and status—but never include your bearer token.

Empty results

No result can reflect incomplete imports, an unsupported mapping, a missing directly reported period, or an ambiguous value that was omitted. It is not proof that the company reported zero. Inspect the original filing and check the coverage guide.