---
title: "Get rolling release configuration"
method: GET
path: "/v1/projects/{idOrName}/rolling-release/config"
tags: ["rolling-release"]
---

# Get rolling release configuration

`GET /v1/projects/{idOrName}/rolling-release/config`

Get the Rolling Releases configuration for a project. The project-level config is simply a template that will be used for any future rolling release, and not the configuration for any active rolling release.

## Path parameters

- `idOrName` string, required — Project ID or project name (URL-encoded)

## Query parameters

- `teamId` string
- `slug` string

## Response `200`

- object
  - `rollingRelease` object, nullable, required — Project-level rolling release configuration that defines how deployments should be gradually rolled out
    - `target` string, required — The environment that the release targets, currently only supports production. Adding in case we want to configure with alias groups or custom environments.
    - `stages` object[], nullable — An array of all the stages required during a deployment release. Each stage defines a target percentage and advancement rules. The final stage must always have targetPercentage: 100.
      - `targetPercentage` number, required — The percentage of traffic to serve to the canary deployment (0-100)
      - `requireApproval` false | true — Whether or not this stage requires manual approval to proceed
      - `duration` number — Duration in minutes for automatic advancement to the next stage
      - `linearShift` false | true — Whether to linearly shift traffic over the duration of this stage
    - `canaryResponseHeader` false | true — Whether the request served by a canary deployment should return a header indicating a canary was served. Defaults to `false` when omitted.

## Other responses

- `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`
- `410`

## Changes

- **2026-07-21** `2ae10ee9d21c` — 1 info
  - added the non-success response with the status `410`

[Change history](https://skmtc.dev/vercel/apis/api/changes/v1/projects/:idOrName/rolling-release/config/get.md)

---

[API](https://skmtc.dev/vercel/apis/api.md) · [All operations](https://skmtc.dev/vercel/apis/api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/vercel/api/revisions/dc85585fad8d/schema)