Get rolling release billing status

APIs & SDKs

GEThttps://api.vercel.com/v1/projects/{idOrName}/rolling-release/billing

Get the Rolling Releases billing status for a project. The team level billing status is used to determine if the project can be configured for rolling releases.

https://api.vercel.com/v1/projects/{idOrName}/rolling-release/billing

const response = await fetch('https://api.vercel.com/v1/projects/idOrName/rolling-release/billing?teamId=string&slug=string', {
  method: 'GET',
  headers: {
    'Authorization': 'Bearer YOUR_ACCESS_TOKEN',
    'Content-Type': 'application/json',
  },
});

const data = await response.json();
console.log(data);

Response

{
  "availableSlots": "0",
  "message": "string",
  "reason": "plan_not_supported"
}

Authentication

AuthorizationbearerToken

Default authentication mechanism

Path parameters

idOrNamestringRequired

Project ID or project name (URL-encoded)

Query parameters

teamIdstringOptional

The Team identifier to perform the request on behalf of.

slugstringOptional

The Team slug to perform the request on behalf of.

Response

200Success

availableSlotsnumberRequired

messagestringRequired

reasonstringRequired

Errors

400One of the provided values in the request query is invalid.

401The request is not authorized.

403You do not have permission to access this resource.

404Error

410Error

Cross-link map: Get rolling release billing status (/docs/rest-api/rolling-release/get-rolling-release-billing-status)

From the Vercel docs graph (built 2026-10-14T10:24:21.026Z), spanning vercel.com docs + KB, nextjs.org, ai-sdk.dev, and other Vercel documentation sites. Full graph as JSON: https://vercel.com/docs/graph.json

Semantically closest pages

Get rolling release configuration — GET /v1/projects/{idOrName}/rolling-release/config — Get the Rolling Releases configuration for a project. The project-l
Get the active rolling release information for a project — GET /v1/projects/{idOrName}/rolling-release — Return the Rolling Release for a project, regardless of whether the rollou
Update the rolling release settings for the project — PATCH /v1/projects/{idOrName}/rolling-release/config — Update \(or disable\) Rolling Releases for a project. When disabl
Complete the rolling release for the project — POST /v1/projects/{idOrName}/rolling-release/complete — Force-complete a Rolling Release. The canary deployment will beg
Start a rolling release for the project — POST /v1/projects/{idOrName}/rolling-release/start — Start a rolling release for a deployment. If a rolling release is a

This page links to (1)

Vercel REST API Reference — Interact programmatically with your Vercel account using the SDK or direct HTTP requests.

Pages that link here (2)

By site: vercel-docs (2)

Vercel REST API Reference — Interact programmatically with your Vercel account using the SDK or direct HTTP requests.
Rolling Releases — Learn how to use Rolling Releases for more cautious deployments.

https://api.vercel.com/v1/projects/{idOrName}/rolling-release/billing

const response = await fetch('https://api.vercel.com/v1/projects/idOrName/rolling-release/billing?teamId=string&slug=string', {
  method: 'GET',
  headers: {
    'Authorization': 'Bearer YOUR_ACCESS_TOKEN',
    'Content-Type': 'application/json',
  },
});

const data = await response.json();
console.log(data);

Response

{
  "availableSlots": "0",
  "message": "string",
  "reason": "plan_not_supported"
}

OpenAPI Specification