Delete a deployment
⚠️
Preview — this feature is being built; the design below is the spec.
DELETE https://app.syntic.ai/v1/deployments/{deployment_id}Delete a deployment. Sessions it already created are kept.
For how this fits into a full workflow, see Scheduled and triggered runs.
Headers
| Header | Required | Value |
|---|---|---|
Authorization | Yes | Bearer <key>: a private inference key (sk_live_...). See Authentication. |
syntic-beta | Yes, while in preview | agents-2026-11-01. Without it the call fails with 400 beta_required. See Versioning. |
Path parameters
| Parameter | Type | Description |
|---|---|---|
deployment_id | string | The deployment id, starting with dep_. |
Response
200 OK, Content-Type: application/json
{
"id": "dep_01JC9E2G4J6L8N0Q2S4U",
"type": "deployment_deleted"
}Examples
curl -sS -X DELETE https://app.syntic.ai/v1/deployments/dep_01JC9E2G4J6L8N0Q2S4U \
-H "Authorization: Bearer $SYNTIC_API_KEY" \
-H "syntic-beta: agents-2026-11-01"Errors
Errors use the error envelope and carry a request_id. Codes specific to this operation:
| Status | type | code | When |
|---|---|---|---|
| 400 | invalid_request_error | beta_required | The syntic-beta header is missing. |
| 404 | not_found_error | deployment_not_found | No deployment with that id in this workspace. |
| 401 | authentication_error | invalid_api_key | The key is missing, unknown, revoked or expired. |
| 429 | rate_limit_error | rate_limited | Too many requests; wait for Retry-After. See Rate-limit headers. |
Was this page helpful?