API Reference

Complete REST API reference for the Bivariant platform — endpoints for agents, flows, collections, integrations, conversations, and more.

This section provides the complete REST API reference for the Bivariant platform. Every endpoint is documented with request parameters, response schemas, and examples.

Resource groups

GroupDescription
AgentsCreate, update, and manage AI agents
AppsInstall and configure apps from blueprints
API KeysManage programmatic access credentials
ArtifactsBrowse and acquire marketplace artifacts
AssetsUpload, download, and organize files
AuthenticationSign in, sign up, and manage sessions
BlueprintsDefine and manage app blueprints
ChannelsConfigure messaging channels
CollectionsManage collections, fields, and records
ConfigsRead and update platform configuration
ConversationsCreate rooms, send messages, manage participants
DatasetsManage structured bulk data storage
DatasourcesConfigure external data sources
FlowsBuild and execute automation workflows
FormsDefine and manage form schemas
IAMManage users, roles, and permissions
IntegrationsConnect to third-party services
KPIsDefine and track key performance indicators
ObjectsWork with platform objects
PipelinesConfigure data pipelines
PreferencesManage user and workspace preferences
PresenceConfigure the web chat widget
ProjectsManage workspace projects
ScreensDefine UI screen layouts
StateManage application state
StoreBrowse and interact with the marketplace
TasksTrack and manage background tasks
TelephonyManage phone numbers and SIP trunks

Authentication

All API requests require authentication. Include your access token or API key in the Authorization header:

Authorization: Bearer {token}

See Authentication for details on obtaining tokens, and API Keys for programmatic access.

Base URL

https://api.bivariant.com/v1

Common patterns

Pagination

List endpoints return paginated results. Use limit and offset query parameters to navigate:

GET /collections/{collectionId}/records?limit=50&offset=100

Error responses

Errors follow a consistent format:

{
  "error": {
    "code": "not_found",
    "message": "The requested resource was not found."
  }
}
Status codeMeaning
400Bad request — invalid parameters
401Unauthorized — missing or invalid token
403Forbidden — insufficient permissions
404Not found — resource does not exist
429Rate limited — too many requests
500Internal error — unexpected server failure