Skip to main content
Use this endpoint to push file changes to an already-deployed application without creating a brand-new deployment. You upload a ZIP archive (or a single file) containing the changed files, and Virtus Cloud applies the update and reloads the application. This is the recommended workflow for iterating on an existing deployment. The endpoint is rate-limited to 1 request every 3 seconds — build in a short delay if you are automating successive commits.
The commit operation replaces files in the application’s working directory. Make sure your ZIP archive contains the correct directory structure for your project so that files land in the right locations on the server.

​
Endpoint

POST https://api.virtuscloud.app/v2/apps/{app_id}/commit

​
Path parameters

​
app_id
string
required
The unique ID of the application. You can find this in the URL of your application’s dashboard page on Virtus Cloud.

​
Request headers

​
Authorization
string
required
Your Virtus Cloud API key. See Authentication for details.
​
Content-Type
string
required
Must be multipart/form-data when sending files via a form upload.

​
Body parameters

​
file
file
required
The file or archive to commit. You can provide either a single file or a ZIP archive containing multiple files. Pass this as a multipart/form-data field using FormData in the browser/Node.js or a Buffer in Node.js.

​
Response

​
status
string
Indicates whether the request succeeded. Returns "success" when the commit is accepted and the files are being applied to the application.
​
message
string
An optional human-readable message providing additional context about the commit result.

​
Code example

curl --request POST \
  --url https://api.virtuscloud.app/v2/apps/<app_id>/commit \
  --header "Authorization: <your_api_key>" \
  --form "file=@./commit.zip"

​
Response example

{
  "status": "success"
}