Skip to main content
POST
Commit files to an application
string
required
The API key for your account. You can find this in your account settings.
Requires an API key with the apps:deploy scope. Commit streams a single file or a .zip archive into an existing application without recreating it. A .zip is unpacked at the destination directory, while any other file is written as-is. This makes it the fastest way to push small code changes, hotfixes, or configuration updates from a CI pipeline or deploy script. Committing does not restart the application by itself: after sending your changes, call Restart Application so the new files take effect. For a first deployment of a new application, use Upload Application instead, and to edit a single file in place without re-uploading, see the File Manager endpoints. Uploads are limited to 100 MB per file. The request body is limited to 101 MB (a file of up to 100 MB plus form overhead): a larger request is rejected with 413 FILE_TOO_LARGE while it is still uploading. Only the first file part is read; additional form fields are ignored. File names containing path traversal (..), path separators, or control characters are rejected before any change is applied. On workspace-shared applications, the caller needs the maintain or admin role.

Parameters

string
required
The ID of the application. You can find this in the URL of your application’s dashboard.
file
required
Use FormData or NodeJS Buffer (single file or compress [zip])
string
Optional. The destination directory inside the application. A .zip is unpacked here; any other file is placed at path/filename. Defaults to the application root.

Response

string
Indicates whether the call was successful: success if it was, error if not.

Common errors