> For the complete documentation index, see [llms.txt](https://integrations.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.impact.com/agency-v3/readme/status-and-error-codes.md).

# Status & Error Codes

impact.com APIs may raise errors for various reasons, such as a failed pathing, invalid parameters, authentication errors, and network unavailability. When a request returns an error, the system will provide a message to indicate more details about the failure. If there are particular errors found, they will be listed in the `Errors` array.

### HTTP Status Code Summary

| Code                  | Status             | Description                                                                                                                                 |
| --------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- |
| 🟢 200                | OK                 | Everything worked as expected.                                                                                                              |
| 201                   | OK                 | Everything worked as expected.                                                                                                              |
| 🔴 400                | Bad request        | Often missing a required parameter.                                                                                                         |
| 🔴 401                | Unauthorized       | No valid API key provided.                                                                                                                  |
| 🔴 402                | Request failed     | Parameters were valid but request failed.                                                                                                   |
| 🔴 403                | Forbidden          | Returned by scoped tokens if they are disabled, or if the scoped token is enabled, but the specific endpoint is not enabled for that token. |
| 🔴 404                | Not found          | The requested resource doesn’t exist.                                                                                                       |
| 🔴 405                | Method not allowed | Method used in the call is not supported.                                                                                                   |
| 🔴 429                | Too many requests  | Too many requests hit the API too quickly. Reduce your requests significantly.                                                              |
| 🔴 500, 502, 503, 504 | Server errors      | Something went wrong on impact.com’s end.                                                                                                   |

While system errors are rare, we recommend writing code that gracefully handles all possible API exceptions. In many cases, these mean implementing a retry mechanism with an exponential drop-off in frequency.

### Error Response Example

{% tabs %}
{% tab title="JSON" %}

```json
{
  "Status": "ERROR",
  "Message": "Validation Failed",
  "Errors": [
    {
      "Field": "AccountId",
      "Message": "Not a numeric value"
    }
  ]
}
```

{% endtab %}

{% tab title="XML" %}

```xml
<ImpactRadiusResponse>
    <Status>ERROR</Status>
    <Message>Validation Failed</Message>
    <Errors>
        <Error>
      <Field>AccountId</Field>
      <Message>Not a numeric value</Message>
    </Error>
    </Errors>
</ImpactRadiusResponse>
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://integrations.impact.com/agency-v3/readme/status-and-error-codes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.