Introduction
How mods, servers and tools talk to ModKey, and what every answer looks like.
Every call is plain HTTPS, no SDK needed. Building a mod? Begin with the key check. Working from a server? Read authentication, then the API v2 overview.
Choose an interface
Connect
The key check your mod calls on launch. No API key needed.
POST /{soft_id}/connect
API v2
Software owners manage software, keys, domains and client accounts from a server.
Reference as JSON
The whole reference in one file for scripts and AI tools.
/docs/agent.json
Basics
- One URL per interface
- API v2 is a single
POST https://dev.mod.wtf/api/v2/actionand themethodfield picks the action. Connect isPOST https://dev.mod.wtf/{soft_id}/connect. - Two response shapes
- API v2 answers
{"ok": true, "data": …}or{"ok": false, "error": …}. Connect answers with astatusboolean. - JSON or form
- API v2 reads JSON and also parses form bodies. Connect takes
application/x-www-form-urlencodedonly. - Dates
- Dates are
Y-m-d H:i:sstrings, for example2026-06-01 12:00:00. - Paging
- List actions take
limit(1 to 200, default 50) andoffset, and answer withtotal,limit,offsetanditems. - Durations are days
- A negative duration means hours.
lifetimemeans the key never expires.