Before you create a deployment you need to upload the required files for that deployment. To do it, you need to first upload each file to this endpoint. Once that’s completed, you can create a new deployment with the uploaded files. The file content must be placed inside the body of the request. In the case of a successful response you’ll receive a status code 200 with an empty body.
Default authentication mechanism
The file size in bytes
The file SHA1 used to check the integrity
40
The file SHA1 used to check the integrity
40
The file size as an alternative to Content-Length
Shared secret token set by v0 deployments. When present and valid, the API applies an extended rate limit.
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"
The body is of type file
.
File already uploaded File successfully uploaded
The response is of type object
.
The response is of type object
.
The response is of type object
.
Before you create a deployment you need to upload the required files for that deployment. To do it, you need to first upload each file to this endpoint. Once that’s completed, you can create a new deployment with the uploaded files. The file content must be placed inside the body of the request. In the case of a successful response you’ll receive a status code 200 with an empty body.
Default authentication mechanism
The file size in bytes
The file SHA1 used to check the integrity
40
The file SHA1 used to check the integrity
40
The file size as an alternative to Content-Length
Shared secret token set by v0 deployments. When present and valid, the API applies an extended rate limit.
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"
The body is of type file
.
File already uploaded File successfully uploaded
The response is of type object
.
The response is of type object
.
The response is of type object
.