Skip to main content

Get Version

Retrieve a single version by its ID.

Path Parameters

string
required
The version ID

Response

string
The version’s unique ID
string
The ID of the project this version belongs to
string
The version’s name/title
string
The version number (e.g., “1.0.0”)
string
The version’s changelog (Markdown)
string
Version type: release, beta, or alpha
string
Version status: listed, archived, draft, unlisted, scheduled, unknown
Whether this version is featured
array
List of compatible mod loaders (e.g., [“fabric”, “quilt”])
array
List of version dependencies
array
List of files in this version
string
ISO 8601 timestamp of publication
integer
Download count

Example Request

Example Response


Get Multiple Versions

Retrieve multiple versions by their IDs.

Query Parameters

string
required
JSON array of version IDs as a string
boolean
Whether to include changelog text (default: true)

Example Request


Get Project Versions

Get all versions for a project with optional filtering.

Path Parameters

string
required
The project ID or slug

Query Parameters

string
JSON array of loaders to filter by (e.g., ["fabric","quilt"])
Filter to only featured versions
string
Filter by version type: release, beta, or alpha
integer
Maximum number of versions to return
integer
Offset for pagination
string
JSON object of loader fields to filter by (e.g., {"game_versions":["1.20.4"]})
boolean
Whether to include changelog (default: true)

Example Request


Get Version by Number

Get a specific version by project and version number.

Path Parameters

string
required
The project ID or slug
string
required
The version number or version ID

Example Request


Create Version

Create a new version for a project. Requires authentication and VERSION_CREATE scope.

Request Body (multipart/form-data)

JSON
required
Version metadata as JSON:
file
required
One or more file parts (referenced in file_parts)

Example Request


Update Version

Update version metadata. Requires authentication and VERSION_WRITE scope.

Path Parameters

string
required
The version ID

Request Body

string
New version name (1-64 characters)
string
New version number (1-32 characters)
string
New changelog (max 65536 characters)
string
New version type: release, beta, or alpha
array
New dependencies list (max 4096)
array
New loaders list
Set featured status
string
New status
array
Update file types for existing files
integer
Custom ordering value

Example Request


Delete Version

Delete a version. Requires authentication and VERSION_DELETE scope.

Path Parameters

string
required
The version ID

Example Request


Upload File to Version

Add additional files to an existing version. Requires authentication.

Path Parameters

string
required
The version ID

Request Body (multipart/form-data)

JSON
Optional file metadata
file
required
The file to upload

Common Use Cases

Publishing a New Version
  1. Prepare version metadata (name, version number, changelog)
  2. Build and test your mod/modpack files
  3. Create version via POST /v3/version with multipart form data
  4. Wait for automatic validation and processing
Managing Dependencies
  • Use project_id for general dependency on any version
  • Use version_id for specific version requirement
  • Use file_name for external dependencies
  • Types: required (must have), optional (recommended), incompatible (conflicts), embedded (bundled)
Loader Fields Loader-specific fields can be passed as flattened properties:
  • game_versions: Array of Minecraft versions (e.g., [“1.20.4”, “1.20.3”])
  • Other loader-specific fields depend on the loader type
File Types
  • Primary file: Main mod/modpack JAR
  • required-resource-pack: Must be installed with the mod
  • optional-resource-pack: Optional companion resource pack
Version Ordering
  • Versions are typically ordered by date_published (newest first)
  • Use ordering field for custom sort order
  • Use featured flag to highlight important versions