Authorizations
Default authentication mechanism
Query Parameters
The Team identifier to perform the request on behalf of.
"team_1a2b3c4d5e6f7g8h9i0j1k2l"
The Team slug to perform the request on behalf of.
"my-team-url-slug"
Body
The desired name for the project
100
"a-project-name"
Opt-in to preview toolbar on the project level
Opt-in to production toolbar on the project level
Specifies whether preview deployments are disabled for this project.
The build command for this project. When null
is used this value will be automatically detected
256
256
The dev command for this project. When null
is used this value will be automatically detected
256
Collection of ENV Variables the Project will use
The framework that is being used for this project. When null
is used no framework is selected
The Git Repository that will be connected to the project. When this is defined, any pushes to the specified connected Git Repository will be automatically deployed
The install command for this project. When null
is used this value will be automatically detected
256
Opts-out of the message prompting a CLI user to connect a Git repository in vercel link
.
The Vercel Auth setting for the project (historically named "SSO Protection")
The output directory of the project. When null
is used this value will be automatically detected
256
Specifies whether the source code and logs of the deployments for this project should be public or not
The name of a directory or relative path to the source code of your project. When null
is used it will default to the project root
256
The region to deploy Serverless Functions in this project
4
Specifies whether Zero Config Failover is enabled for this project.
OpenID Connect JSON Web Token generation configuration.
Opt-in to skip deployments when there are no changes to the root directory and its dependencies
Specifies resource override configuration for the project
Response
The project was successfuly created
22.x
, 20.x
, 18.x
, 16.x
, 14.x
, 12.x
, 10.x
, 8.10.x
Retention policies for deployments. These are enforced at the project level, but we also maintain an instance of this at the team level as a default policy that gets applied to new projects.
blitzjs
, nextjs
, gatsby
, remix
, react-router
, astro
, hexo
, eleventy
, docusaurus-2
, docusaurus
, preact
, solidstart-1
, solidstart
, dojo
, ember
, vue
, scully
, ionic-angular
, angular
, polymer
, svelte
, sveltekit
, sveltekit-1
, ionic-react
, create-react-app
, gridsome
, umijs
, sapper
, saber
, stencil
, nuxtjs
, redwoodjs
, hugo
, jekyll
, brunch
, middleman
, zola
, hydrogen
, vite
, vitepress
, vuepress
, parcel
, fastapi
, fasthtml
, sanity-v3
, sanity
, storybook
, nitro
, hono
, express
, h3
, xmcp
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 1
- Option 2
Description of why a project was rolled back, and by whom. Note that lastAliasRequest contains the from/to details of the rollback.
Project-level rolling release configuration that defines how deployments should be gradually rolled out
- Option 1
- Option 2
standard
, advanced
, critical
- Option 1
- Option 2