Reference
Errors
Use HTTP status codes to decide whether a request should be corrected, authenticated again or retried.
Code
Meaning
Guidance
200
Success
The request was processed successfully.
400
Bad Request
The JSON body or submitted value is invalid.
401
Unauthorized
The x-api-key header is missing or the key is invalid.
403
Forbidden
The API key or organisation is disabled or inactive.
404
Not Found
The requested route does not exist.
429
Too Many Requests
A rate or connection limit has been exceeded.
500
Internal Server Error
The billing/application layer could not complete the transaction.
502
Bad Gateway
The underlying ThreatPrevent risk service could not be reached or returned an error.
Retry strategy
Correct 4xx requests rather than retrying them unchanged. For transient 5xx or 502 responses, use limited exponential backoff and avoid uncontrolled retry loops that could create duplicate workflow activity.