- Integrations (v1): GitHub integrations and repository listings
- Deployments (v2): Create, manage, and update Agent Server deployments
- Listeners (v2): Listener resources for self-hosted enterprise organizations
- Auth Service (v2): OAuth provider configuration and authentication flows
Host
The control plane hosts for Cloud data regions:| Region |
|---|
| GCP US |
| GCP EU |
| GCP APAC |
| AWS US |
/api-host. For example, http(s)://<host>/api-host/v2/deployments. See the self-host usage guide for more details.
Authentication
To authenticate with the control plane API, set theX-Api-Key header to a valid LangSmith API key and set the X-Tenant-Id header to a valid workspace ID to target.
Example curl command:
Versioning
Each endpoint path is prefixed with a version (e.g.v1, v2).
Quick start
- Call
POST /v2/deploymentsto create a new Deployment. The response body contains the Deployment ID (id) and the ID of the latest (and first) revision (latest_revision_id). - Call
GET /v2/deployments/{deployment_id}to retrieve the Deployment. Setdeployment_idin the URL to the value of Deployment ID (id). - Poll for revision
statusuntilstatusisDEPLOYEDby callingGET /v2/deployments/{deployment_id}/revisions/{latest_revision_id}. - Call
PATCH /v2/deployments/{deployment_id}to update the deployment.
Resource spec
Theresource_spec object sets CPU, memory, and replica counts for a deployment’s API servers, queue workers, Redis, and PostgreSQL. The field descriptions in the Deployments (v2) reference list each field. The following behaviors apply across fields:
PATCHreplaces the whole object: APATCHthat includesresource_specreplaces the storedresource_specand does not merge with it. Fields you leave out fall back to the defaults for the deployment type, not to their previous values. Send the fullresource_specon everyPATCH.- Limits default to 2x the request: If you set a CPU or memory request and omit its limit, the limit defaults to 2x the request. The Redis memory limit is the exception:
redis_memory_limit_mbdefaults toredis_memory_mb. On self-hosted data planes, the CPU limit also sets the autoscaling target. - CPU values are rounded to 1 decimal place: Rounding uses floating-point arithmetic, so some values round down. For example,
0.25is stored as0.2. - Redis memory has its own range:
redis_memory_mbandredis_memory_limit_mbaccept 512 to 16384, in multiples of 128. The API enforces this range in a validator, so it does not appear in the OpenAPI schema.
resource_spec again with the rules of its own version. A PATCH that returns 200 can still fail at deploy time on an older listener. See Listener version requirements.
To mount persistent storage, such as Amazon EFS, into a self-hosted deployment’s pods, set volumes and volume_mounts in resource_spec. For more information, see Volumes.
Example Code
Below is example Python code that demonstrates how to orchestrate the control plane APIs to create a deployment, update the deployment, and delete the deployment.Connect these docs to your agent of choice via MCP for real-time answers.

