Create a Vercel deployment via the Vercel API or deploy hook
domain: vercel.com/docs · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
For deploy hooks: create a hook in the Vercel project Settings > Git > Deploy Hooks, specifying a name and target branch; Vercel provides a unique URL
Trigger via POST to the deploy hook URL with an empty body or optional JSON body containing 'buildCache: false' to bypass cache; no authentication header is needed (URL is the secret)
For the REST API: create a deployment via POST to 'https://api.vercel.com/v13/deployments' with header 'Authorization: Bearer YOUR_TOKEN'
Include in the JSON body: 'name' (project name), 'gitSource' object with 'type', 'repoId', and 'ref', plus 'projectId' to link to an existing project
Poll GET '/v13/deployments/{deploymentId}' checking the 'readyState' field for 'READY', 'ERROR', or 'CANCELED'
Known gotchas
Deploy hook URLs contain a secret path component; treat them as credentials — rotating them invalidates all integrations using the old URL
The REST API deployment endpoint requires either file uploads (for framework-agnostic deployments) or a git source reference; mixing the two or omitting required fields returns a 400
Vercel enforces concurrent deployment limits per account tier; exceeding the limit queues deployments, which may cause unexpected delays in CI pipelines expecting immediate builds
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?