HomeGetting startedRegistering with an HTTP keyGetting a credential without DiscordServer claim flowReport rules and the block windowVersion check and 426Authentication and server keysThe blocking modelError handlingRate limitsVersions and compatibilityPOST /v1/servers/claimPOST /v1/servers/reportPOST /v1/servers/revokePOST /plugin/v1/claimPOST /plugin/v1/reportGET /plugin/v1/versionGET /maps/{seed}GET /jobs/{seed}GET /seedsGET /stats/overviewGET /stats/protectionAPI changelog
Blocking API
POST
/api/v1/servers/revoke
Revokes this server key. Whoever holds the key can end it, whether it came from self-claim or from a Discord HTTP key. Reports with a revoked key get 401. This cannot be undone.
Request headers
| Header | Value | Description |
|---|---|---|
| Authorization | Bearer slsrv_… | The server key to revoke. |
| User-Agent | MyServer/1.0 | Recommended. Your implementation name and version. |
Request body
No request body.
Responses
| Status | Body | When |
|---|---|---|
| 200 | {"ok":true} | Revoked. The key no longer works. |
| 401 | {"error":"invalid credential"} | No key, an unknown key, or a key that was already revoked. |
| 429 | {"error":"rate limited"} | More than 20 per minute from this IP. Retry after Retry-After. |
| 503 | {"error":"db unavailable"} | Retry shortly. |
Response fields
| Field | Type | null | Description |
|---|---|---|---|
| ok | boolean | no | Always true. |
Example
curl -X POST https://slmaps.com/api/v1/servers/revoke -H "Authorization: Bearer slsrv_..." -H "User-Agent: MyServer/1.0"
Response example
{
"ok": true
}What the plugin does
Use it to end a leaked key. A self-claim key is reissued by claiming the same IP:port again; a Discord HTTP key is reissued from the Discord panel. It may be sent from any IP; only the key matters.
SLMAPS is the seed-map viewer for SCP: Secret Laboratory. These pages describe the public API of slmaps.com.slmaps.com ·