mirror of
https://github.com/discountry/ritmex-bot.git
synced 2026-09-09 16:28:06 +00:00
38 lines
2.8 KiB
Markdown
38 lines
2.8 KiB
Markdown
---
|
||
title: "Session Authentication | Binance Open Platform"
|
||
source: "https://developers.binance.com/docs/binance-spot-api-docs/websocket-api/session-authentication"
|
||
fetched_at: "2026-02-26T10:38:13.356Z"
|
||
---
|
||
**Note:** Only _Ed25519_ keys are supported for this feature.
|
||
|
||
If you do not want to specify `apiKey` and `signature` in each individual request, you can authenticate your API key for the active WebSocket session.
|
||
|
||
Once authenticated, you no longer have to specify `apiKey` and `signature` for those requests that need them. Requests will be performed on behalf of the account owning the authenticated API key.
|
||
|
||
**Note:** You still have to specify the `timestamp` parameter for `SIGNED` requests.
|
||
|
||
### Authenticate after connection[](https://developers.binance.com/docs/binance-spot-api-docs/websocket-api/session-authentication)
|
||
|
||
You can authenticate an already established connection using session authentication requests:
|
||
|
||
- [`session.logon`](https://developers.binance.com/docs/binance-spot-api-docs/websocket-api/session-authentication) – authenticate, or change the API key associated with the connection
|
||
- [`session.status`](https://developers.binance.com/docs/binance-spot-api-docs/websocket-api/session-authentication) – check connection status and the current API key
|
||
- [`session.logout`](https://developers.binance.com/docs/binance-spot-api-docs/websocket-api/session-authentication) – forget the API key associated with the connection
|
||
|
||
**Regarding API key revocation:**
|
||
|
||
If during an active session the API key becomes invalid for _any reason_ (e.g. IP address is not whitelisted, API key was deleted, API key doesn't have correct permissions, etc), after the next request the session will be revoked with the following error message:
|
||
|
||
```
|
||
{ "id": null, "status": 401, "error": { "code": -2015, "msg": "Invalid API-key, IP, or permissions for action." }}
|
||
```
|
||
|
||
### Authorize _ad hoc_ requests[](https://developers.binance.com/docs/binance-spot-api-docs/websocket-api/session-authentication)
|
||
|
||
Only one API key can be authenticated with the WebSocket connection. The authenticated API key is used by default for requests that require an `apiKey` parameter. However, you can always specify the `apiKey` and `signature` explicitly for individual requests, overriding the authenticated API key and using a different one to authorize a specific request.
|
||
|
||
For example, you might want to authenticate your `USER_DATA` key to be used by default, but specify the `TRADE` key with an explicit signature when placing orders.
|
||
|
||
- [Authenticate after connection](https://developers.binance.com/docs/binance-spot-api-docs/websocket-api/session-authentication)
|
||
- [Authorize _ad hoc_ requests](https://developers.binance.com/docs/binance-spot-api-docs/websocket-api/session-authentication)
|