Create a new version
POST /version
This route creates a new version of the engine. Each new version must include at least one attached file, except when the new version’s status is draft
.
The file_id
field, which uniquely identifies each file, must be specified and can be obtained from the API release page.
Authorizations
Request Body required
object
object
Name of the version
The version number. Ideally will follow semantic versioning
The changelog for this version
A direct URL to the changelog for this version
The release channel for this version
The current status of the version
URL to the GitHub release
List of files associated with the version
object
Unique identifier for the file
Target platform for the file (e.g., Windows, Linux, macOS)
Architecture for the file (e.g., x86, x64, arm64)
Hash (e.g., SHA-512) for verifying file integrity
Responses
200
Version created successfully
object
Name of the version
The version number. Ideally will follow semantic versioning
The changelog for this version
A direct URL to the changelog for this version
The release channel for this version
The current status of the version
A unique identifier for this version, using the CUID2 format
The unique identifier of the author who published this version, formatted as CUID2
The date this version was published, in ISO 8601 format
A list of files available for download for this version
object
Hash (e.g., SHA-512) for verifying file integrity
A direct link to the file
The name of the file
The size of the file in bytes
Architecture for the file (e.g., x86, x64, arm64)
URL to the GitHub release
400
Request was invalid, see given error
object
A short error code or message indicating the type of error
A detailed message explaining the reason for the error
403
Forbidden - You are not authorized to create this version.