Open · OpenAPI 3.0
BetaOS API
Integrate BetaOS into your existing tool landscape.
Every entity in BetaOS — cells, roles, services, targets, employees — is available through a stable RESTful API. Use it to connect existing systems, automate workflows, or build entirely new applications on top of the BetaOS operating model.
BetaOS API v1
OpenAPI 3.0 GET /v1/cells Cells
POST /v1/cells Cells
GET /v1/cells/{id} Cells
GET /v1/roles Roles
PUT /v1/roles/{id} Roles
POST /v1/services Services
GET /v1/targets Targets
PATCH /v1/targets/{id} Targets
GET /v1/economic-buyers Buyers
POST /v1/webhooks Webhooks
Authorization: Bearer bos_live_e7a9c…f3b1 scoped
POST /v1/cells
"name": "Enterprise",
"kind": "periphery",
"buyer": "market"
201 Created application/json
{
"id": "cell_4d9f",
"name": "Enterprise",
"kind": "periphery",
"buyer": "market",
"created_at": "2026-05-19T08:42Z"
}
Overview
The API is fully documented to OpenAPI 3.0 with interactive examples and SDK-friendly response shapes. It is open by design: no artificial restrictions, no vendor lock-in, no separate enterprise tier for basic features. Companies, developers, researchers, and consultants can all build on the same stable contract.
Key features
- RESTful endpoints for every BetaOS entity
- OpenAPI 3.0 specification with interactive docs
- Token-based auth with role-aware scopes
- Webhooks for entity-change events
- Generous rate limits with transparent quotas
- Backward-compatible versioning policy
Use cases
- Syncing teams and roles between BetaOS and Personio/Workday
- Pushing structural changes from BetaOS into Slack or Confluence
- Building custom visualizations and reports
- Automating onboarding workflows triggered by role assignments