https://code.deepline.com
Call this API from a trusted backend service, serverless function, notebook, or scheduler.
Use the CLI or SDK for local Play files.
These interfaces bundle and check the source before they submit it.
This page describes the shared HTTP contract.
Each provider guide describes its connection requirements and checked tool IDs.
The guide also describes required payloads, approval rules, and side effects.
Authentication and security
Send a workspace API key with every request:Inspect a tool before you execute it
The live contract defines tool IDs, input schemas, and Deepline prices.- Search for the tool.
- Read
GET /api/v2/integrations/{toolId}/get. - Check the provider guide’s approval rules and side effects.
Inspect a public tool contract
Read the tool’s schema before you execute the tool. This metadata request 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.
For another tool, first read GET /api/v2/integrations/{toolId}/get.
Then call POST /api/v2/integrations/{toolId}/execute with the 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. Representative excerpt:
Read Play-run status
URL-encoderun.id. Request the canonical run endpoint with the encoded ID:
ENCODED_RUN_ID:
run.status from the response. completed, failed, and cancelled are
terminal statuses. The default response is the compact package: outputs and
datasets are package fields. Dataset rows have their own paginated endpoints.
Explicit ?full=true selects the legacy detail wrapper. Read these fields in that response:
status: the run status.package.run.statusalso contains the run status.result: the final output.package.outputs: the compact outputs.
run object.
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.