https://code.deepline.com
Use this API from a trusted backend service, serverless function, notebook, or
scheduler. For local Play files, use the CLI or SDK
so Deepline can bundle and validate the source first.
This page owns the shared HTTP contract. Each provider guide
owns its connection, verified tool IDs, payload requirements, approval rules,
and side effects.
Authentication and security
Send a workspace API key with every request:Inspect a tool before you execute it
Tool IDs, input schemas, and Deepline pricing are live contracts. Search for a tool, readGET /api/v2/integrations/{toolId}/get, then confirm the provider
guide’s approval and side-effect notes. Do not guess a payload from an old blog
post or retry an ambiguous provider mutation blindly.
Inspect a public tool contract
Read a tool’s schema before you execute it. This is a metadata request: it does not execute the tool or create a charge.free_simple_company_search is a public, discoverable tool. Its returned
inputSchema describes the required sql field. When you deliberately execute
that tool, use the path-routed endpoint and this request envelope:
POST /api/v2/integrations/execute is not supported for new callers. For any
other tool, first inspect GET /api/v2/integrations/{toolId}/get, then use
POST /api/v2/integrations/{toolId}/execute with its documented input schema.
Start a saved or prebuilt Play
Start an already saved Play withPOST /api/v2/plays/run. Deepline-managed
prebuilt Plays must use the prebuilt/ namespace.
play_run package. Read its public run ID from run.id:
Read Play-run status
URL-encoderun.id, then request the canonical run endpoint:
ENCODED_RUN_ID:
run.status from the response. completed, failed, and cancelled are
terminal statuses. The full response includes the run package and outputs.
Environment variables
DEEPLINE_API_KEY: workspace-scoped bearer key.- Provider credentials: configure them only for the providers your workspace uses. Each provider guide documents its authentication requirement.