---
title: "Point production traffic to a given deployment"
method: POST
path: "/v10/projects/{projectId}/promote/{deploymentId}"
tags: ["projects"]
---

# Point production traffic to a given deployment

`POST /v10/projects/{projectId}/promote/{deploymentId}`

## Request

- Base URL: `https://api.vercel.com`
- URL: `https://api.vercel.com/v10/projects/{projectId}/promote/{deploymentId}`
- Auth: HTTP bearer

Allows users to promote a deployment to production. Note: This does NOT rebuild the deployment. If you need that, then call create-deployments endpoint.

## Path parameters

- `projectId` string, required
- `deploymentId` string, required

## Query parameters

- `teamId` string
- `slug` string

## Response `201`

## Other responses

- `202`
- `400`: One of the provided values in the request query is invalid.
- `401`: The request is not authorized.
- `403`: You do not have permission to access this resource.
- `404`
- `409`
- `410`
- `422`

## Changes

- **2026-09-30** `099fbe1f521c`: 1 info
  - added the non-success response with the status `404`
- **2026-08-19** `6b6e0450635c`: 1 info
  - added the non-success response with the status `422`
- **2026-07-21** `2ae10ee9d21c`: 1 info
  - added the non-success response with the status `410`
- **2025-10-09** `50caddad4ae7`: 1 warning, 1 info
  - deleted the `query` request parameter `dangerouslyForcePromoteCanary`
  - added the success response with the status `202`
- **2025-05-17** `67f6a93c3cd8`: 1 info
  - added the new optional `query` request parameter `dangerouslyForcePromoteCanary`

[Operation history](https://skmtc.dev/vercel/apis/vercel-api/changes/v10/projects/:projectId/promote/:deploymentId/post.md)

---

[API](https://skmtc.dev/vercel/apis/vercel-api.md) - [All operations](https://skmtc.dev/vercel/apis/vercel-api/llms.txt) - [OpenAPI document](https://skmtc.dev/vercel/apis/vercel-api/revisions/60686c0e1f6a?raw)