Skip to main content
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

Enterprise limits, volume pricing, and bespoke arrangements are all negotiable. Start at support.octaviatech.app.

​
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.
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.

​
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 401.
  • Does the role allow it? A valid key with the wrong role returns 403. See Teams & API keys.
  • Is the service active? An inactive workspace returns 423.
  • Is it a quota, not a throttle? 426 is a plan limit and will not clear on its own. See Plans.
  • Is the path right? The /cms segment is required. See 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.

GitHub

Report an issue or find the SDK sources.

Support portal

Open a ticket with the engineering team.

​
Status

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

Octavia on X

Service announcements and incidents.
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.