HTTP Status Codes
Every error is an RFC 9457 problem document with a correlationId. Quote the ID when reporting an issue to your AggKnowledge account team so we can find the exact request.
Exception: person enrichment endpoints answer invalid input (400) with the enrichment problem flags described in Enrichment Errors, not a problem document.
| Status | Name | Description | Retryable? |
|---|---|---|---|
| 200 | OK | Request succeeded. Check isSuccess for data-level success. | — |
| 400 | Bad Request | Invalid request — malformed JSON, invalid or missing required fields, or a missing/malformed x-api-key. The title and detail fields say which. | No — fix input |
| 401 | Unauthorized | The key is well-formed but not valid — unknown, disabled, or revoked. (A missing or malformed key returns 400.) | No — check key |
| 402 | Payment Required | Insufficient credits or subscription doesn’t cover this endpoint. | No — add credits |
| 404 | Not Found | The requested resource could not be found. | No |
| 429 | Too Many Requests | Rate limit exceeded. Check the X-Rate-Limit-Retry-After-Seconds header. | Yes — after delay |
| 500 | Server Error | Unexpected server error. | Yes — with backoff |