FullHunt uses standard HTTP status codes to indicate whether a request succeeded, failed validation, lacked authorization, exceeded limits, or hit a temporary service issue.

​
Error Response

Most error responses include a JSON body with a status code and message:
Error response
Some middleware-generated responses, such as rate-limit responses, may use a more specific error body:
Rate limit response

​
Client Errors

​
Server Errors

​
Retry Guidance

1

Retry only recoverable failures

Retry 429, 500, 502, and 503 responses. Do not blindly retry 400, 401, 403, or 404 responses without correcting the request.
2

Use backoff

Increase delay between retries and add jitter so multiple workers do not retry at the same time.
3

Preserve request context

Log the endpoint, status code, response message, and request identifier if your infrastructure adds one. Do not log API keys.

​
Production Checklist

  • Validate inputs before sending requests to FullHunt.
  • Set a client-side timeout for every request.
  • Treat authentication and authorization failures as configuration issues, not transient errors.
  • Use rate-limit guidance to pace scheduled jobs and background workers.
  • Keep enough response context in logs to debug failures without exposing secrets.