Overview
Endpoint reference for the Deadlock Mod Manager HTTP API
API Reference
Each endpoint page shows the request and response schema and includes a playground for sending test requests.
API Information
Routes are served under https://api.deadlockmods.app/api and return JSON.
Mod, download and status routes need no authentication.
Quick Start
Example Request
curl "https://api.deadlockmods.app/api/v2/mods"Example Response
GET /v2/mods returns every mod as a JSON array. It takes no pagination, search or filter parameters. One element, with most fields omitted:
[
{
"remoteId": "512345",
"name": "Example Skin",
"author": "ExampleAuthor",
"category": "Skins",
"downloadCount": 1542,
"remoteUpdatedAt": "2026-01-20T14:45:00.000Z"
}
]The List Mods V2 page lists every field.
API Categories
The API is organized into several categories:
Mods API
List mods and get a single mod
Downloads API
Get download links for a mod
Profile API
Share and load mod profiles
System API
Health check, version and status
API Versions
New integrations should use the /v2 routes. The /v1 routes remain available: GET /v1/mods and GET /v1/mods/{id} return the same data as their v2 equivalents, and GET /v1/mods/{id}/download returns only the largest file of a mod.
Rate Limits
Only some routes are rate limited, per client IP; the mod listing is not. Limited routes return RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset (seconds until the window resets), and a rejected request returns HTTP 429 with Retry-After. The integration guide lists each limit.
Error Handling
Errors use oRPC's JSON body, and the HTTP status matches status:
{
"defined": false,
"code": "NOT_FOUND",
"status": 404,
"message": "Not Found"
}Getting Support
Need help with the API?