Skip to main content

API Reference

The Bedrock API is a REST API for building and managing autonomous AI agents.

Base URL

Authentication

Bedrock supports two authentication schemes:
  • API Key (most use cases) — send Authorization: Bearer YOUR_API_KEY using an organization-scoped key from /api/organizations/api-keys/.
  • Token Auth (portal / user-scoped) — DRF TokenAuthentication; send Authorization: Token YOUR_USER_TOKEN. Tokens are returned by /api/organizations/auth/signup/ and /api/organizations/auth/login/.
Endpoints like /api/organizations/organizations/, /api/organizations/api-keys/, and /api/templates/ accept either scheme. See Authentication for details.

Request Format

Headers

Request Body

Send JSON for POST, PUT, and PATCH requests:

Response Format

Success Response

List Response (Paginated)

Error Response

Validation errors include field details:

HTTP Status Codes


Organizations

Base path: /api/organizations/

Auth

Organizations

Organization API Keys

Members

Invites


Templates

Base path: /api/templates/ AgentTemplates blueprint new agents. Their configuration is snapshotted onto each agent at creation time.

Agents

Base path: /api/cloud/

Agents

Usage Records


Adapters & Tools

Base path: /api/toolbox/

Adapters

Adapter Configs

Per-template configuration (API keys, phone numbers, etc.) for an adapter. Creating an AdapterConfig both enables the adapter on the template and stores its config. Delete the row to detach the adapter.

Tools


Tracing

Base path: /api/tracing/

Traces

Spans

Span types: text, audio, tool, function, llm, checkpoint. See Evaluations for the checkpoint span shape.

Trace Reviews

Human (or automated) review attached to any trace. Rubric scores live in criterion_scores; checkpoint_pass_rate and weighted_score are computed on read from the trace’s span_type="checkpoint" spans and the review’s scores respectively.

Legacy Eval Cases

A small read/write endpoint for stand-alone Eval records. Bedrock no longer runs end-to-end simulations (those live in the bedrock-harness repo) — this endpoint is kept for storing individual eval inputs/rubrics.

Default Adapter State

Base path: /api/defaults/ REST endpoints for data managed by the built-in adapters. Agents interact with this state through tools; these endpoints let your own backend read/write the same data.

Contacts

Documents

Projects

Notifications

See Notifications for semantics.

SMS / MMS / Surge / Blooio Messages

Inbound + outbound history for each messaging adapter.

Email Messages

Webchat

Local web-based chat channel (alternative to SMS for dev / testing).

OAuth — Gmail / Google Calendar / Drive / Strava

Connect per-user third-party accounts to an agent. Each adapter follows the same shape.

OpenAPI Specification

The complete OpenAPI 3.0 spec powers this reference and is also available at:
  • Interactive Docs: https://api.bedrock.orinlabs.org/api/docs/
  • ReDoc: https://api.bedrock.orinlabs.org/api/redoc/
  • Raw Schema: https://api.bedrock.orinlabs.org/api/schema/