Skip to main content
The Octavia Developer Platform is a set of backend services you activate from one dashboard and call over one consistent API. Each service is activated independently, scoped with your own API key, and metered on its own plan — so you start with exactly what you need and turn on the rest when you outgrow it.

Octavia Developers Hub

The product surface behind the APIs.

​
One platform, several services

AI CMS is the only service with a full reference today. Everything else is activated from the dashboard and will get its own tab here as its reference lands.

​
What every service has in common

Whichever service you pick, the shape of the work is the same.
  • One dashboard. dashboard.octaviatech.app is where you activate services, create keys, and watch usage.
  • One team per workspace. Every resource belongs to a team, and keys belong to that team — see Teams & API keys.
  • One key per service. A key is scoped to a single service, so a key for another Octavia product never counts against your AI CMS allowance.
  • One header. Every call is authenticated with x-api-key. There is no second header for you to set — see Authentication.
  • One envelope. Every service answers with the same { success, statusCode, message, data } shape, so your error handling is written once — see Response format.

​
How to read this documentation

The docs are split into two tabs, and they answer different questions.
Ready to make a call? The Quickstart walks a new workspace from sign-up to a working API key in about five minutes.

​
Conventions used across the docs

A few things hold everywhere, so they are stated once.
  • Identifiers are 24-character hex strings (MongoDB ObjectIds), passed in the path or the body.
  • Slugs are URL-facing and unique. Most create endpoints accept one explicitly; some derive it from the name.
  • Multilingual fields are maps from a language code to a string, e.g. { "en": "Hello", "es": "Hola" }.
  • Timestamps are ISO 8601 in UTC.
  • x-api-key is the only header you send. Multi-tenancy headers are attached by the gateway, and no SDK option accepts them.

Quickstart

From sign-up to a working key.

Teams & API keys

How access is structured across a workspace.