Update specific version of application
Update an existing specific version of an application with new artifacts and metadata.
warning
You cannot change app_name
, channel
and version
. app_name
and version
are used for correct searching.
Endpoint
POST /apps/update
Authentication
Header | Value |
---|---|
Authorization | Bearer <jwt_token> |
Request Body
The request uses multipart/form-data
format with the following fields:
Field | Type | Required | Description |
---|---|---|---|
file | file | ❌ | App binary file(s) |
app_name | string | ✅ | Name of the application |
version | string | ✅ | Version of the application |
channel | string | ❌ | Channel (e.g., stable, beta) |
publish | boolean | ❌ | Marks the version available for users |
critical | boolean | ❌ | Marks the version as critical |
platform | string | ❌ | Platform (e.g., linux, windows) |
arch | string | ❌ | Architecture (e.g., amd64, arm64) |
changelog | string | ❌ | Changelog in markdown format |
Example Request
Single File Upload
curl --location 'http://localhost:9000/apps/update' \
--header 'Authorization: Bearer <jwt_token>' \
--form 'data="{\"id\": \"653a6268f51dee6a99a3d88c\", \"app_name\": \"secondapp\", \"version\": \"0.0.2\", \"channel\": \"stable\", \"publish\": true, \"platform\": \"linux\", \"arch\": \"amd64\", \"changelog\": \"\"}"' \
--form 'file=@"/path_to_file/secondapp.deb"'
Multiple File Upload
curl --location 'http://localhost:9000/apps/update' \
--header 'Authorization: Bearer <jwt_token>' \
--form 'data="{\"id\": \"653a6268f51dee6a99a3d88c\", \"app_name\": \"secondapp\", \"version\": \"0.0.2\", \"channel\": \"stable\", \"publish\": true, \"platform\": \"linux\", \"arch\": \"amd64\", \"changelog\": \"\"}"' \
--form 'file=@"/path_to_file/secondapp.deb"' \
--form 'file=@"/path_to_file/secondapp.rpm"'
Response
Success Response (200 OK)
{
"updatedResult.Updated": true
}
Response Fields
Field | Type | Description |
---|---|---|
updatedResult.Updated | boolean | Indicates whether the version was successfully updated |
Notes
- You can upload multiple files for different platforms/architectures in a single request
- The
changelog
field supports markdown formatting - Critical versions are typically used for security updates or critical bug fixes
- Published versions are immediately available to end users
- Only the fields you provide will be updated - omitted fields remain unchanged