Skip to main content
POST
Regenerate keys
Universal endpoint for regenerating API and/or WebSocket tokens. The previous token is canceled, and all associated settings, subscriptions and rights restrictions are transferred to the newly generated token.

Authorization

The erlcrussia-api-key header is not strictly required if you are regenerating the WebSocket key. You can pass:
  • erlcrussia-api-key - for regenerating the HTTP API key (?api=true).
  • erlcrussia-websocket-key - for regenerating the WebSocket key (?websocket=true).
  • Or both headers with simultaneous regeneration (?api=true&websocket=true).

Query parameters

At least one of the parameters (?api=true or ?websocket=true) is required. When transferring ?api=true&websocket=true, both keys will be regenerated simultaneously.
A key may be rotated once every five minutes; respect Retry-After on 429. Successful rotation is audited with key ID and IP, without the secret.

Authorizations

erlcrussia-api-key
string
header
required

Custom API key. Store on the server; do not include client-side JavaScript.

Query Parameters

api
boolean

Перегенерировать HTTP API ключ

websocket
boolean

Перегенерировать WebSocket ключ

Response

Token(s) have been successfully regenerated.

success
boolean
message
string
oldToken
string
newToken
string
token
string
apiKey
string
key
string
userId
string
serverId
string