API Reference
Subbasis API usage is centered on workflow execution, controlled actions, and operational state access.
What this means
The API surface is workflow-oriented. It is not only a thin wrapper around prompts or raw model calls.
Why it matters
Teams integrating Subbasis usually need:
- lifecycle control of workflow executions
- runtime visibility and status checks
- governed external actions via connectors
- reviewable records for operations
How Subbasis handles it
API patterns are typically aligned with:
- workflow definitions and execution lifecycle
- agent task orchestration
- approval and policy-aware action flow
- evidence and trace access patterns
- integration boundaries for connectors/adapters
Reference scope
- Workflow-oriented operations
- Execution status and review paths
- Connector and integration boundaries
Configuration / usage model
When using API integrations, define:
- execution ownership model (who starts/approves/stops)
- connector permission boundaries
- idempotency and retry strategy
- evidence requirements for critical operations
Limits and deployment notes
- Endpoint catalog and availability can vary by release/deployment mode.
- Usage envelopes remain plan-dependent.
- Use official release notes for exact endpoint-level behavior.