> ## Documentation Index
> Fetch the complete documentation index at: https://docs.creatoraudit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Support

> How to get help — what to check first, and what to include when you email us.

Stuck on something? Most questions have a fast self-serve answer; when you do need
us, a couple of details make the difference between a quick fix and a long
back-and-forth.

## Check these first

<Columns cols={2}>
  <Card title="FAQ" href="/faq" icon="circle-question">
    Common questions about tracking, metrics, freshness, and billing.
  </Card>

  <Card title="Errors" href="/api-reference/errors" icon="triangle-exclamation">
    What each status code and `code` means, and how to fix it.
  </Card>
</Columns>

For account, organization, or API-key issues, the [dashboard](https://app.creatoraudit.com)
is usually the quickest path — manage keys on [API keys](/dashboard/api-keys).

## Email support

If you still need a hand, email
[support@creatoraudit.com](mailto:support@creatoraudit.com).

To help us trace the problem, always include:

* **The `X-Request-ID`** from the failing response. Every response carries one — read
  it from the response headers (for an error, it's also echoed in the body). It lets
  us find the exact request in our logs.
* **The endpoint and timestamp** — for example `POST /v2/accounts` at
  `2026-06-15T14:03:00Z`.
* **What you expected vs. what happened**, and the full error body if you have it.

```bash theme={null}
# The X-Request-ID is in the response headers:
curl -i https://api.creatoraudit.com/v2/whoami \
  -H "Authorization: Bearer YOUR_API_KEY"
# -> X-Request-ID: 7f3a…
```

<Note>
  Never share your full API key in an email or screenshot. The `X-Request-ID` and the
  endpoint are enough for us to find the request.
</Note>