title: API ## Resources * [How the Minetest client uses the API](https://github.com/minetest/contentdb/blob/master/docs/minetest_client.md) ## Responses and Error Handling If there is an error, the response will be JSON similar to the following with a non-200 status code: ```json { "success": false, "error": "The error message" } ``` Successful GET requests will return the resource's information directly as a JSON response. Other successful results will return a dictionary with `success` equaling true, and often other keys with information. For example: ```js { "success": true, "release": { /* same as returned by a GET */ } } ``` ## Authentication Not all endpoints require authentication, but it is done using Bearer tokens: ```bash curl https://content.minetest.net/api/whoami/ \ -H "Authorization: Bearer YOURTOKEN" ``` Tokens can be attained by visiting [Settings > API Tokens](/user/tokens/). * GET `/api/whoami/`: JSON dictionary with the following keys: * `is_authenticated`: True on successful API authentication * `username`: Username of the user authenticated as, null otherwise. * 4xx status codes will be thrown on unsupported authentication type, invalid access token, or other errors. ## Packages * GET `/api/packages/` (List) * See [Package Queries](#package-queries) * GET `/api/packages///` (Read) * PUT `/api/packages///` (Update) * Requires authentication. * JSON dictionary with any of these keys (all are optional, null to delete Nullables): * `type`: One of `GAME`, `MOD`, `TXP`. * `title`: Human-readable title. * `name`: Technical name (needs permission if already approved). * `short_description` * `tags`: List of [tag](#tags) names. * `content_warnings`: List of [content warning](#content-warnings) names. * `license`: A [license](#licenses) name. * `media_license`: A [license](#licenses) name. * `long_description`: Long markdown description. * `repo`: Git repo URL. * `website`: Website URL. * `issue_tracker`: Issue tracker URL. * `forums`: forum topic ID. * GET `/api/packages///dependencies/` * If query argument `only_hard` is present, only hard deps will be returned. You can download a package by building one of the two URLs: ``` https://content.minetest.net/packages/${author}/${name}/download/` https://content.minetest.net/packages/${author}/${name}/releases/${release}/download/` ``` Examples: ```bash # Edit package curl -X PUT https://content.minetest.net/api/packages/username/name/ \ -H "Authorization: Bearer YOURTOKEN" -H "Content-Type: application/json" \ -d '{ "title": "Foo bar", "tags": ["pvp", "survival"], "license": "MIT" }' # Remove website URL curl -X PUT https://content.minetest.net/api/packages/username/name/ \ -H "Authorization: Bearer YOURTOKEN" -H "Content-Type: application/json" \ -d '{ "website": null }' ``` ### Package Queries Example: /api/packages/?type=mod&type=game&q=mobs+fun&hide=nonfree&hide=gore Supported query parameters: * `type`: Package types (`mod`, `game`, `txp`). * `q`: Query string. * `author`: Filter by author. * `tag`: Filter by tags. * `random`: When present, enable random ordering and ignore `sort`. * `limit`: Return at most `limit` packages. * `hide`: Hide content based on [Content Flags](/help/content_flags/). * `sort`: Sort by (`name`, `title`, `score`, `reviews`, `downloads`, `created_at`, `approved_at`, `last_release`). * `order`: Sort ascending (`asc`) or descending (`desc`). * `protocol_version`: Only show packages supported by this Minetest protocol version. * `engine_version`: Only show packages supported by this Minetest engine version, eg: `5.3.0`. * `fmt`: How the response is formated. * `keys`: author/name only. * `short`: stuff needed for the Minetest client. ## Releases * GET `/api/releases/` (List) * Limited to 30 most recent releases. * Optional arguments: * `author`: Filter by author * `maintainer`: Filter by maintainer * Returns array of release dictionaries with keys: * `id`: release ID * `title`: human-readable title * `release_date`: Date released * `url`: download URL * `commit`: commit hash or null * `downloads`: number of downloads * `min_minetest_version`: dict or null, minimum supported minetest version (inclusive). * `max_minetest_version`: dict or null, minimum supported minetest version (inclusive). * `package` * `author`: author username * `name`: technical name * `type`: `mod`, `game`, or `txp` * GET `/api/packages///releases/` (List) * Returns array of release dictionaries, see above, but without package info. * GET `/api/packages///releases//` (Read) * POST `/api/packages///releases/new/` (Create) * Requires authentication. * Body can be JSON or multipart form data. Zip uploads must be multipart form data. * `title`: human-readable name of the release. * For Git release creation: * `method`: must be `git`. * `ref`: (Optional) git reference, eg: `master`. * For zip upload release creation: * `file`: multipart file to upload, like ``. * `commit`: (Optional) Source Git commit hash, for informational purposes. * You can set min and max Minetest Versions [using the content's .conf file](/help/package_config/). * DELETE `/api/packages///releases//` (Delete) * Requires authentication. * Deletes release. Examples: ```bash # Create release from Git curl -X POST https://content.minetest.net/api/packages/username/name/releases/new/ \ -H "Authorization: Bearer YOURTOKEN" -H "Content-Type: application/json" \ -d '{ "method": "git", "title": "My Release", "ref": "master" }' # Create release from zip upload curl -X POST https://content.minetest.net/api/packages/username/name/releases/new/ \ -H "Authorization: Bearer YOURTOKEN" \ -F title="My Release" -F file=@path/to/file.zip # Create release from zip upload with commit hash curl -X POST https://content.minetest.net/api/packages/username/name/releases/new/ \ -H "Authorization: Bearer YOURTOKEN" \ -F title="My Release" -F commit="8ef74deec170a8ce789f6055a59d43876d16a7ea" -F file=@path/to/file.zip # Delete release curl -X DELETE https://content.minetest.net/api/packages/username/name/releases/3/ \ -H "Authorization: Bearer YOURTOKEN" ``` ## Screenshots * GET `/api/packages///screenshots/` (List) * Returns array of screenshot dictionaries with keys: * `id`: screenshot ID * `approved`: true if approved and visible. * `title`: human-readable name for the screenshot, shown as a caption and alt text. * `url`: absolute URL to screenshot. * `created_at`: ISO time. * `order`: Number used in ordering. * GET `/api/packages///screenshots//` (Read) * Returns screenshot dictionary like above. * POST `/api/packages///screenshots/new/` (Create) * Requires authentication. * Body is multipart form data. * `title`: human-readable name for the screenshot, shown as a caption and alt text. * `file`: multipart file to upload, like ``. * DELETE `/api/packages///screenshots//` (Delete) * Requires authentication. * Deletes screenshot. * POST `/api/packages///screenshots/order/` * Requires authentication. * Body is a JSON array containing the screenshot IDs in their order. Currently, to get a different size of thumbnail you can replace the number in `/thumbnails/1/` with any number from 1-3. The resolutions returned may change in the future, and we may move to a more capable thumbnail generation. Examples: ```bash # Create screenshot curl -X POST https://content.minetest.net/api/packages/username/name/screenshots/new/ \ -H "Authorization: Bearer YOURTOKEN" \ -F title="My Release" -F file=@path/to/screnshot.png # Delete screenshot curl -X DELETE https://content.minetest.net/api/packages/username/name/screenshots/3/ \ -H "Authorization: Bearer YOURTOKEN" # Reorder screenshots curl -X POST https://content.minetest.net/api/packages/username/name/screenshots/order/ \ -H "Authorization: Bearer YOURTOKEN" -H "Content-Type: application/json" \ -d "[13, 2, 5, 7]" ``` ## Reviews * GET `/api/packages///reviews/` (List) * Returns array of review dictionaries with keys: * `user`: dictionary with `display_name` and `username`. * `title`: review title * `comment`: the text * `is_positive`: boolean * `created_at`: iso timestamp * `votes`: dictionary with `helpful` and `unhelpful`, * GET `/api/reviews/` (List) * Above, but for all packages. * Each review has a `package` dictionary with `type`, `author` and `name` Example: ```json [ { "comment": "This is a really good mod!", "created_at": "2021-11-24T16:18:33.764084", "is_positive": true, "title": "Really good", "user": { "display_name": "rubenwardy", "username": "rubenwardy" }, "votes": { "helpful": 0, "unhelpful": 0 } } ] ``` ## Topics * GET `/api/topics/` ([View](/api/topics/)): Supports [Package Queries](#package-queries), and the following two options: * `show_added`: Show topics which exist as packages, default true. * `show_discarded`: Show topics which have been marked as outdated, default false. ### Topic Queries Example: /api/topics/?q=mobs Supported query parameters: * `q`: Query string. * `sort`: Sort by (`name`, `views`, `date`). * `order`: Sort ascending (`asc`) or descending (`desc`). * `show_added`: Show topics that have an existing package. * `show_discarded`: Show topics marked as discarded. * `limit`: Return at most `limit` topics. ## Types ### Tags * GET `/api/tags/` ([View](/api/tags/)): List of: * `name`: technical name * `title`: human-readable title * `description`: tag description or null ### Content Warnings * GET `/api/content_warnings/` ([View](/api/content_warnings/)): List of: * `name`: technical name * `title`: human-readable title * `description`: tag description or null ### Licenses * GET `/api/licenses/` ([View](/api/licenses/)): List of: * `name` * `is_foss`: whether the license is foss ### Minetest Versions * GET `/api/minetest_versions/` ([View](/api/minetest_versions/)) * `name`: Version name. * `is_dev`: boolean, is dev version. * `protocol_version`: protocol version umber. ## Misc * GET `/api/scores/` ([View](/api/scores/)) * See [Top Packages Algorithm](/help/top_packages/). * Supports [Package Queries](#package-queries). * Returns list of: * `author`: package author name. * `name`: package technical name. * `downloads`: number of downloads. * `score`: total package score. * `score_reviews`: score from reviews. * `score_downloads`: score from downloads. * GET `/api/homepage/` ([View](/api/homepage/)) - get contents of homepage. * `count`: number of packages * `downloads`: get number of downloads * `new`: new packages * `updated`: recently updated packages * `pop_mod`: popular mods * `pop_txp`: popular textures * `pop_game`: popular games * `high_reviewed`: highest reviewed