> 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:

<figure><img src="/files/vKQoSMUZiABQGa4qciBR" alt="" width="204"><figcaption></figcaption></figure>

***

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.

<figure><img src="/files/fNO0fUfJzyuDXZu9EmiT" alt=""><figcaption></figcaption></figure>

{% 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 %}

***

## Rate Limiting

* **Rate limit:** 600 requests per minute, shared across your entire organization (all users and API tokens in your organization count against the same limit).
* **When you hit the limit:** The API returns HTTP 200 with a JSON-RPC error in the response body:

  <pre class="language-json" data-overflow="wrap"><code class="lang-json">{ "error": { "code": -32002, "message": "Too many requests for this tenant; try again later." } }
  </code></pre>

  Requests resume automatically once the 60-second window resets.


---

# 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=<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.