Log in with API key
Authenticate WebSocket connection using the provided API key.
After calling session.logon, you can omit apiKey and signature parameters for future requests that require them.
Note that only one API key can be authenticated.
Calling session.logon multiple times changes the current authenticated API key.
Note: Only Ed25519 keys are supported for this feature.
Log in with API key › Authorization
Log in with API key › Request Weight
This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.
Learn more in the Rate limits section.
Log in with API key › Request Parameters optional
idClient-generated request identifier.
methodWebSocket API method name.
Log in with API key › Responses
Log in with API key
idstatusLog out of the session
Forget the API key previously authenticated. If the connection is not authenticated, this request does nothing.
Note that the WebSocket connection stays open after session.logout request. You can continue using the connection, but now you will have to explicitly provide the apiKey and signature parameters where needed.
Log out of the session › Request Weight
This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.
Learn more in the Rate limits section.
Log out of the session › Request Parameters optional
idClient-generated request identifier.
methodWebSocket API method name.
paramsLog out of the session › Responses
Log out of the session
idstatusQuery session status
Query the status of the WebSocket connection, inspecting which API key (if any) is used to authorize requests.
Query session status › Request Weight
This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.
Learn more in the Rate limits section.
Query session status › Request Parameters optional
idClient-generated request identifier.
methodWebSocket API method name.
paramsQuery session status › Responses
Query session status
idstatus