Deployments
Deploy the App
Publishes the App to production and waits until the new version serves. By default, the request first commits any changes in the sandbox, then publishes that commit; pass commit_id to publish an earlier version. Publishing an unpublished App puts it back online.
POST
Deploy the App
Authorizations
Scopes
Headers
A key that identifies this request for retries, up to 200 printable characters. A retry with the same key and input returns the first request's result instead of repeating the work. If you omit the key, the API generates one and returns it in the Idempotency-Key response header.
Required string length:
1 - 200Path Parameters
Body
application/json
Response
The deployment.
Where the deployment is:
publishing: the version is being built and published, after any database migrations that must run first.starting: production points to this version, and it's starting.succeeded: the version started serving. It stayssucceededafter a later deployment replaces it or the App is unpublished. To see which deployment is serving now, check the App'sproduction.deployment_id.failed: the version wasn't published, or it didn't start serving.errorsays why.disabled: the App was deleted while the version was publishing, so it never served.
Available options:
publishing, starting, succeeded, failed, disabled