What this API is for
The Omium HTTP API sits alongside the Python SDK and CLI. Use it when you want to list executions, drive replays from your own orchestrator, or integrate Omium into a service written in any language. Day-to-day tracing still flows through the SDK in production apps.Base URL
Authentication
Available resources
These endpoints are documented in detail on the pages linked in the sidebar.| Area | Use it | Primary paths |
|---|---|---|
| Executions | Start runs, inspect status, replay or roll back from checkpoints | GET/POST /executions, /executions/{id}/replay |
| Checkpoints | List checkpoints, fetch state for recovery | GET /checkpoints, GET /checkpoints/{id} |
| Workflows | Register and version workflows you push from projects | GET/POST/PUT/DELETE /workflows |
| Failures | Investigate failed runs and track resolution | GET /failures, GET /failures/stats |
| Billing | Read balances, usage, and subscription state | GET /billing/* |
Client libraries
For Python, install the official package so headers, paths, and retries stay consistent:OMIUM_API_KEY and OMIUM_API_URL when you call omium.init() without arguments. See Python SDK and CLI reference for everything the shipped client can do.
Minimal request
List recent executions (empty list is normal on a new account):Errors and limits
- Expect regular HTTP status codes (
401for bad keys,404for unknown IDs,429when throttled). - For platform-wide throughput and spend, see your dashboard and API keys & billing.
Next steps
Quickstart
Run a traced workflow locally in a few minutes.
Executions API
Request and response shapes for runs and replays.
Python SDK
Instrument LangGraph, CrewAI, or your own code.
Platform capabilities
Map features to APIs and dashboard surfaces.