Deployments

Deploy a site

Builds and publishes the site's current main branch to production. Asynchronous: responds 202 with a pending deployment; poll GET /sites/{id}/deployments for the outcome (live or failed).

If a deploy is already in flight, that one is returned instead of starting a second build — still 202. A build this call started is pending with a null started_at; one already running is building.

post/sites/{id}/deploy

Request

  • Base URL: https://api.crevio.co/v1
  • URL: https://api.crevio.co/v1/sites/{id}/deploy
  • Auth: API key in header Authorization

Path parameters

idstring required

The resource ID (e.g., "prod_abc123") or slug (e.g., "my-product")

Headers

Idempotency-Keystring

Makes this write safe to retry: a repeat with the same key replays the first response instead of creating a second resource. Scoped to the account, remembered for 24 hours; reusing a key with a different payload is an error.

Response

The queued deployment

idstring required
objectstring required
sitestring required
status'pending' | 'building' | 'live' | 'failed' | 'superseded' | 'unpublished' required
commit_shastring nullable required
is_liveboolean required
urlstring nullable required
triggered_bystring nullable required
error_messagestring nullable required
db_bookmarkstring nullable required
current_stagestring nullable required
duration_secondsnumber nullable required
elapsed_secondsnumber nullable required
started_atstring nullable required
finished_atstring nullable required
created_atstring required

Changes

No recorded changes to this operation across all 2 revisions of this API.