Error handling
The MuleHunt API uses standard HTTP status codes. Error responses use a JSON object with an error value that includes a code and message.
| Status code | Meaning | Recommended action |
|---|---|---|
400 | Invalid query criteria, including an unsupported field such as status. | Send only the documented q fields. |
401 | Authentication failed. | Check the access token and obtain a new one if needed. |
403 | The partner does not have the MuleHunt Scam Baiting service enabled. | Contact your MuleHunt administrator. |
429 | Rate limit exceeded. | Wait and retry with exponential backoff. |
500 | Unexpected server error. | Retry later; contact support if the error persists. |
The API uses the data-access scope assigned to your partner. Filters outside that scope return an empty successful result, rather than data outside your permission. Any client-supplied order is ignored; results always use the server-defined ordering.