Stop deployment
Stop a running preview deployment. Stopped deployments keep their
configuration and can be resumed later with startDeployment.
The deployment must be ready and running, and must belong to a non-production environment; production deployments cannot be stopped. A deployment that is already draining from a previous stop is rejected with a precondition error.
Stopping is asynchronous: this endpoint only enqueues the stop and returns
immediately. Poll getDeployment until the status reaches stopped.
Required Permissions
Your root key must have one of the following permissions:
environment.*.stop_deployment(to stop deployments in any environment)environment.<environment_id>.stop_deployment(to stop deployments in a specific environment)
Authorizations
Unkey uses bearer tokens for authentication. Public integrations use root keys, while the dashboard proxy uses short-lived JWTs. To authenticate, include the token in the Authorization header of each request:
Root keys have specific permissions attached to them, controlling what operations they can perform. Legacy permissions use tuple strings like api.*.create_key; resource permissions use Unkey Resource Names plus actions, like unkey:v1:ws_123:keyspaces/*#create_key.
Security best practices:
- Keep root keys secure and never expose them in client-side code
- Use different root keys for different environments
- Rotate keys periodically, especially after team member departures
- Create keys with minimal necessary permissions following least privilege principle
- Monitor key usage with audit logs.
Body
Stop a running preview deployment to free up resources.
Identifies a resource by either its unique ID or its slug. Accepts a prefixed ID (such as 'proj_' or 'app_') or a slug.
3 - 255^[a-zA-Z0-9_-]+$"proj_1234abcd"
Response
Stop accepted and enqueued. The deployment transitions to stopped
asynchronously; poll getDeployment to observe the transition.
Metadata object included in every API response. This provides context about the request and is essential for debugging, audit trails, and support inquiries. The requestId is particularly important when troubleshooting issues with the Unkey support team.
Empty response object by design. A successful response indicates this operation was successfully executed.