Before triggering a deployment, you must configure at least one deploy target in the Miteos dashboard. Each target requires you to authorize the relevant hosting provider and select a default project or team.
Authentication
All requests require a Bearer token in theAuthorization header.
mt_test_xxx tokens to trigger deployments in sandbox mode — no files are pushed to the hosting provider and the returned url is a preview stub.
POST /deployments
Trigger a new deployment for a workspace. The API queues a build job, pushes the output to your chosen target, and returns the deployment record immediately withstatus: pending.
Request
The ID of the workspace whose build artifact you want to deploy.
The hosting provider to deploy to. Accepted values:
vercel, netlify, cloudflare, expo.The ID of the deploy configuration to use. Configurations are created and managed in the dashboard under Settings → Deployments.
Response
Unique identifier for this deployment record.
The workspace that was deployed.
The hosting provider the build was pushed to.
Current pipeline status. One of
pending, building, deploying, live, or failed.The public URL for the deployment. Populated once
status reaches live; null before that.ISO 8601 timestamp of when the deployment was triggered.
ISO 8601 timestamp of when the pipeline finished (success or failure).
null while the deployment is still in progress.Examples
Example Response
GET /deployments
Return a paginated list of all deployments across your account, ordered bycreated_at descending.
Examples
Example Response
GET /deployments/
Retrieve a single deployment by its ID. Poll this endpoint to track progress through the pipeline stages.Path Parameters
The deployment ID returned when the deployment was created.
Deployment Status Reference
| Status | Description |
|---|---|
pending | Job queued, waiting for a build runner |
building | Running the build step (install, compile, bundle) |
deploying | Uploading the build artifact to the hosting provider |
live | Deployment is publicly accessible at url |
failed | Pipeline encountered an error; check dashboard logs for details |
Examples
Example Response
