Start deployment
Start a deployment that was previously stopped with stopDeployment, so it
serves traffic again. The deployment keeps the configuration it had when it
was stopped; nothing is rebuilt or redeployed.
The deployment must currently be stopped, and must belong to a non-production environment. Production deployments are never stopped, so they cannot be started.
Starting is asynchronous: this endpoint only enqueues the start and returns
immediately. Poll getDeployment until the status reaches ready.
Required Permissions
Your root key must have one of the following permissions:
environment.*.start_deployment(to start deployments in any environment)environment.<environment_id>.start_deployment(to start 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
Start a stopped preview deployment so it serves traffic again.
The stopped deployment to start.
3 - 255^[a-zA-Z0-9_-]+$"proj_1234abcd"
Response
Start accepted and enqueued. The deployment transitions to ready
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.