Interact programmatically with your Vercel account using the SDK or direct HTTP requests.
You can deploy new versions of web applications, manage custom domains, retrieve information about deployments, and manage secrets and environment variables for projects.
The API supports any programming language or framework that can send HTTP requests.
To interact with the API, you can:
Our API is exposed as an HTTP/1 and HTTP/2 service over SSL. All endpoints live under the URL https://api.vercel.com
and then generally follow the REST architecture.
The API supports HTTP versions 1, 1.1, and 2, although HTTP/2 is preferred.
TLS versions 1.2 and 1.3 are supported, with resumption.
For more information on TLS support, refer to the SSL Labs report.
All requests must be encoded as JSON with the Content-Type: application/json header. If not otherwise specified, responses from the Vercel API, including errors, are encoded exclusively as JSON as well.
Vercel Access Tokens are required to authenticate and use the Vercel API.
Access Tokens can be created and managed from inside your account settings.
Setting an expiration date on an Access Token is highly recommended and is considered one of the standard security practices that helps keep your information secure. You can select from a default list of expiration dates ranging from 1 day to 1 year. You can view the expiration date of your Access Tokens on the tokens page.
By default, you can access resources contained within your own user account (personal).
To access resources owned by a team, or create a project for a specific team, you must first find the Team ID.
After you obtained the Team ID, append it as a query string at the end of the API endpoint URL:
If authentication is unsuccessful for a request, the error status code 403 is returned.
Interact programmatically with your Vercel account using the SDK or direct HTTP requests.
You can deploy new versions of web applications, manage custom domains, retrieve information about deployments, and manage secrets and environment variables for projects.
The API supports any programming language or framework that can send HTTP requests.
To interact with the API, you can:
Our API is exposed as an HTTP/1 and HTTP/2 service over SSL. All endpoints live under the URL https://api.vercel.com
and then generally follow the REST architecture.
The API supports HTTP versions 1, 1.1, and 2, although HTTP/2 is preferred.
TLS versions 1.2 and 1.3 are supported, with resumption.
For more information on TLS support, refer to the SSL Labs report.
All requests must be encoded as JSON with the Content-Type: application/json header. If not otherwise specified, responses from the Vercel API, including errors, are encoded exclusively as JSON as well.
Vercel Access Tokens are required to authenticate and use the Vercel API.
Access Tokens can be created and managed from inside your account settings.
Setting an expiration date on an Access Token is highly recommended and is considered one of the standard security practices that helps keep your information secure. You can select from a default list of expiration dates ranging from 1 day to 1 year. You can view the expiration date of your Access Tokens on the tokens page.
By default, you can access resources contained within your own user account (personal).
To access resources owned by a team, or create a project for a specific team, you must first find the Team ID.
After you obtained the Team ID, append it as a query string at the end of the API endpoint URL:
If authentication is unsuccessful for a request, the error status code 403 is returned.