List API keys
GET
/api/api-keysEvery API key, with its owner and state. Never the key itself.
Needs the ManageApiKeys permission.
AuthorizationBearer <token>
An API key, made on Settings, API keys. Every key starts with mbk_.
In: header
Response Body
application/json
application/problem+json
application/problem+json
curl -X GET "https://example.com/api/api-keys"{ "keys": [ { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "name": "string", "start": "string", "permissionNames": [ "string" ], "ownerId": "4d206909-730f-409a-88f6-dcfaa8fc28cc", "ownerName": null, "createdAt": "2019-08-24T14:15:22Z", "expiresAt": null, "lastUsedAt": null, "revokedAt": null, "state": "string" } ], "grantable": [ { "name": "string", "value": 0, "label": "string", "description": "string", "group": "string" } ]}Apply staff roles from Discord POST
Run the pass now, even when it would take roles from many accounts at once. Needs the `ManageUsers` and `ManageRoles` permissions.
Add API key POST
Make a key for yourself. The response carries the key. It is shown this once: only its hash is stored. The key can hold no permission you do not hold, and on every request it is narrowed again to what your account holds at that moment. Needs the `ManageApiKeys` permission.