> For the complete documentation index, see [llms.txt](https://docs.material.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.material.security/reference/api-v1/errors-and-troubleshooting.md).
# Errors and Troubleshooting
## Logs
API events are logged in the [Audit Log](https://docs.material.security/learn-more/administration/audit-log). API related events are indicated next to the Actor with the API icon:
***
API related events are listed in the Audit Log. You can also quickly navigate to token specific events via the tokens list:
1. From **Tokens**, select **one** token row.
2. Click **View Audit Events.**
3. The Audit Log opens, pre-filtered to this token's events within the last week. Update the filter as needed.
{% hint style="warning" %}
The filtered audit log shows results for a single token. Since accounts can have multiple tokens, it may not include all events for a given user.
{% endhint %}
***
## Error responses
Every endpoint returns the same error shape: a JSON body with an `error` field describing what went wrong.
| Status | Meaning | What to check |
| --------------------------- | -------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| `400 Bad Request` | A parameter or request body failed validation | The response includes a `validationFailures` array naming each field that failed |
| `401 Unauthorized` | The API token is missing or invalid | The `x-material-client-secret` header is present and the token is correct |
| `403 Forbidden` | The token is valid, but the account behind it lacks permission | The account's roles. Some endpoints need more than read access, and a few check a per-account setting |
| `404 Not Found` | The resource doesn't exist, or your token can't reach it | The encoded ID, and whether the resource belongs to a tenant your token can access |
| `429 Too Many Requests` | You've sent too many requests in a short period | Slow down and retry. See Rate limiting below |
| `500 Internal Server Error` | Something failed on Material's side | Retry, then contact support if it persists |
A `403` doesn't always mean your token is under-scoped. Two cases are worth knowing:
* Requesting `include=investigation` on an OAuth app needs permission to read investigation data on top of app access. Without it you get a `403` rather than a response with the field quietly missing, so a null value always means there's nothing to show.
* Revoking an account's grant of an OAuth app returns `403` when OAuth App Remediation is turned off for that account. That's a per-account setting, not a property of your token.
***
## Rate limiting
The API is rate limited to protect your instance from bursts of traffic. If you send requests faster than the limit allows, the API returns `429 Too Many Requests` until the traffic settles.
Build retries into any script that runs at volume. Back off when you receive a `429`, then retry rather than continuing at the same rate. Requests succeed again on their own once the burst passes, so a `429` doesn't mean anything is wrong with your token.
{% hint style="info" %}
The [Material MCP server](https://docs.material.security/reference/material-mcp-server) is rate limited separately, with its own limit and its own error format. See [Material MCP Server](https://docs.material.security/reference/material-mcp-server) for details.
{% endhint %}
---
# 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://docs.material.security/reference/api-v1/errors-and-troubleshooting.md?ask=&goal=
```
`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.
