Skip to main content
Use the REST API when Deepline is called from a backend service, serverless function, notebook, Airflow job, warehouse task, or other non-CLI runtime.

Authentication

All public REST endpoints accept a workspace API key as a bearer token:
No request-signing scheme is required for direct server-side calls to tool or play endpoints. Store the API key only in trusted server-side environments. Do not expose it in browser code.

Execute a tool

Tool execution requests use the tool ID in the URL:
The request body wraps the tool input in payload:
Example:
POST /api/v2/integrations/execute is the legacy endpoint and should not be used for new callers.

Deno / Supabase Edge Functions

Execute a saved or prebuilt play

For multi-step workflows, start a play run:
Then poll the returned workflowId:

Environment variables

  • DEEPLINE_API_KEY (workspace-scoped)
  • Per-provider keys are documented in each provider guide (for BYOK providers)
For payload fields on each action, open the provider page under Integrations and pick the operation.