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

# Support

> Where to get help, and what to include so you get it quickly.

If something here is unclear, wrong, or missing, this is the page that tells you the
fastest way to get an answer.

***

## Ask in the right place

| **Your question is about**                    | **Go to**                                                                        |
| --------------------------------------------- | -------------------------------------------------------------------------------- |
| A `4xx` or `5xx` from the API                 | [Status codes](/api-reference/ai-cms/status-codes), then open a ticket           |
| Whether you can retry a failure               | [Rate limits & errors](/api-reference/ai-cms/rate-limits-and-errors)             |
| Hitting <code>426</code> or out of AI credits | Check [Plans](/api-reference/ai-cms/plans), then the dashboard for current usage |
| Which key role you need                       | [Teams & API keys](/platform/teams-and-keys)                                     |
| A term you do not recognise                   | [Glossary](/resources/glossary)                                                  |
| Anything else, or a commercial question       | [support.octaviatech.app](https://support.octaviatech.app)                       |

<Info>
  Enterprise limits, volume pricing, and bespoke arrangements are all negotiable.
  Start at [support.octaviatech.app](https://support.octaviatech.app).
</Info>

***

## Include these and you will get a fast answer

Most slow tickets are slow because the operation could not be reproduced. Four things
make a ticket answerable on the first reply:

1. **The exact request.** Method, full path, and the body — with the API key removed.
2. **The exact response.** The status code and the JSON body, including `data`.
3. **The request ID** from the response headers, if there is one.
4. **Your SDK and version**, if you are using one — for example
   `@octaviatech/cms@1.0.0`.

```bash theme={null}
# A request you can paste into a ticket, with the key out of it.
curl -i https://api.octaviatech.app/cms/articles/getAll?limit=1 \
  -H "x-api-key: YOUR_API_KEY"
```

<Warning>
  Never paste a working API key into a ticket, a screenshot, or a public issue. Redact
  it — a key that has been shared should be treated as compromised and rotated.
</Warning>

***

## Before you open a ticket

A few things are worth checking, because they account for most failures:

* **Is the key active?** A disabled or expired key returns <code>401</code>.
* **Does the role allow it?** A valid key with the wrong role returns <code>403</code>.
  See [Teams & API keys](/platform/teams-and-keys).
* **Is the service active?** An inactive workspace returns <code>423</code>.
* **Is it a quota, not a throttle?** <code>426</code> is a plan limit and will not
  clear on its own. See [Plans](/api-reference/ai-cms/plans).
* **Is the path right?** The <code>/cms</code> segment is required. See
  [Base URL](/api-reference/ai-cms/base-url).

***

## Report a documentation problem

If a page is wrong, ambiguous, or missing something, that is a bug in these docs and
we want it. Tell us which page and what you expected to find instead.

<CardGroup cols={2}>
  <Card title="GitHub" icon="github" href="https://github.com/octaviatech" arrow="true">
    Report an issue or find the SDK sources.
  </Card>

  <Card title="Support portal" icon="headset" href="https://support.octaviatech.app" arrow="true">
    Open a ticket with the engineering team.
  </Card>
</CardGroup>

***

## Status

If calls are failing across the board rather than for your key alone, check the status
of the platform before debugging your integration.

<Card title="Octavia on X" icon="x-twitter" href="https://x.com/octaviatech_app" arrow="true">
  Service announcements and incidents.
</Card>

<Note>
  Multi-tenancy headers such as tenant identity and service status are attached by the
  gateway. If you are debugging a request and find yourself wanting to set one, that
  is the wrong layer — see [Authentication](/api-reference/ai-cms/authentication).
</Note>