Skip to main content
POST
Upload Files to Application
string
required
The ID of the application to upload files to. If the application belongs to a workspace, pass its ID in the workspace_id query parameter.
string
If set to "true", the application will automatically restart after the upload completes.
string
If the application belongs to a workspace, the workspace’s ID. Members with an Owner, Admin or Developer role can use the file manager on a workspace app they don’t own; without this, only the app’s own owner can.
file
required
The file to upload — either a single loose file (written at its target path as-is) or a ZIP archive.A ZIP is extracted on top of the application’s existing volume: files it contains overwrite the matching paths, but files already on disk that aren’t in the ZIP are left untouched — it’s a merge, not a replace. Forbidden directories (node_modules, .git, .local, and similar) are stripped from the ZIP on the server before extraction, regardless of what the archive contains.Multipart upload is capped at 100 MB; a ZIP is also capped at 512 MB once decompressed.

Response

object
The result returned by the host after the upload.

Error Responses

string
The error code indicating the reason for failure. Possible values:
  • UNAUTHORIZED: The user is not authenticated.
  • ACCESS_DENIED: The user does not have access to the application.
  • APP_NOT_FOUND: The specified application does not exist.
  • NO_FILE_UPLOADED: No file was provided in the request (400).
  • INVALID_ZIP_STRUCTURE: The zip could not be read (400).
  • UNKNOWN_ERROR: An unexpected platform error occurred.
  • INTERNAL_SERVER_ERROR: An unexpected server error occurred.