Deploy an App
Queue a build+deploy for an App, creating a new version.
Full deploy workflow:
POST /{app_id}/deploy/upload-url→ get a presigned S3 PUT URL- Upload your built dist/ zip to that URL
- Call this endpoint with the returned
bundle_s3_key - Optionally include
source_files(path→content map) for version diffing - Poll
GET /{app_id}/deploys/{deploy_id}until status iscomplete
Edit-and-redeploy workflow:
GET /{app_id}/versions/{version}/download→ download the bundle zip- Edit files locally
- Re-zip and upload via upload-url → deploy (creates a new version)
GET /{app_id}/versions/{old}/diff/{new}to review changes
Each deploy creates an immutable version record. Use POST /{app_id}/versions/{n}/restore
for instant rollback to any previous version.
Headers
Bearer token authentication using your API key. Format: 'Bearer sk_xxxxxxxxxxxxx'. You can create API keys in the Mixpeek dashboard under Organization Settings.
"Bearer YOUR_MIXPEEK_API_KEY"
Path Parameters
Body
Deploy a pre-built bundle (CLI path) or trigger a Git-based build.
Deploy message describing what changed (required, like a git commit message)
Target environment for this deploy
staging, production Deploy source. 'cli_upload' = zip already uploaded to S3. 'git' = Phase 3b.
cli_upload, git S3 key of the uploaded source zip (required for source='cli_upload')
Map of relative path → file content for source-level version diffs
Git commit SHA associated with this deploy
Git commit message associated with this deploy
Git commit author (name )

