API reference
API overview
Mobius exposes a JSON HTTP API at https://api.mobius.deepnoodle.ai. Every endpoint is
versioned under /v1.
Authentication
All requests require an API key in the Authorization header:
Authorization: Bearer mob_sk_abc123API keys are scoped to a single organization and can optionally be pinned to a single project. Generate them under Settings → API Keys.
Conventions
- Pagination — list endpoints use cursor-based pagination via
cursorandlimitquery parameters. Cursors are opaque base64url strings. - IDs — every resource has a typed ID prefix (
run_,wf_,wkr_, etc.) so you can tell at a glance what kind of thing you're holding. - Errors — non-2xx responses include a JSON body with
code,message, anddetailsfields. - Webhook terminology —
/v1/projects/{handle}/webhooksis the managed inbound webhook resource,/v1/billing/webhookis a billing-specific inbound Stripe receiver, and workflowcallback_urlrefers to an outbound callback concept. See Webhooks.
Example: list workflows
curl https://api.mobius.deepnoodle.ai/v1/workflows \
-H "Authorization: Bearer $MOBIUS_API_KEY" \
-H "Accept: application/json"{
"data": [
{ "id": "wf_01H...", "name": "onboard-customer", "createdAt": "2026-04-01T12:00:00Z" }
],
"nextCursor": null
}Reference
The full OpenAPI spec is published at /openapi.yaml. Generated client SDKs for Go and TypeScript are available in the main repository.