Tutorial · API keys

API keys: drive Cadenio from your own systems

Create a token and Cadenio's REST API is yours: start runs, read status, update fields, and manage members programmatically from any service you build.

4 min read · Developers & admins

API Keys

Create a token in one click

Under Settings, the Integrations tab has an API Keys section. Click New key to create a token to integrate with Cadenio via the REST API. Copy it once, store it securely, and use it as a bearer token from your own code.

The API Keys section of settings with a New key button and a Create your first key call to action — API Keys, under Settings → Integrations. Generate a token to call the REST API from your systems.

What the API can do

Programmatic control

Runs: Start a run, read its status and progress, and complete tasks, all over HTTP.
Fields: Read and update field values on a run, so external systems can feed data in and pull results out.
Members: Manage users and their access programmatically as your org changes.
Full reference: The complete endpoint reference lives in the docs; the API is REST with JSON payloads.

Treat an API key like a password. It is shown once at creation, so store it in a secrets manager, never in client-side code or a public repo. Revoke and rotate a key the moment it may be exposed.

Common questions

Where is the full API reference?

In the documentation, under the Public API page. It lists every endpoint for runs, fields, status, and members, with request and response shapes.

How do I authenticate requests?

Send the API key as a bearer token in the Authorization header. Each request is scoped to the organization the key belongs to.

Build on top of Cadenio

See the REST API drive a run end to end on a guided demo.

Watch guided demo Back to tutorials

Create a token in one click

API Keys, under Settings → Integrations. Generate a token to call the REST API from your systems.

Programmatic control

Runs: Start a run, read its status and progress, and complete tasks, all over HTTP.

Fields: Read and update field values on a run, so external systems can feed data in and pull results out.

Members: Manage users and their access programmatically as your org changes.

Full reference: The complete endpoint reference lives in the docs; the API is REST with JSON payloads.