For more information on why you need session keys, refer to the "API Reference" > "Session Keys".
Managing session keys via UX can easily be done by going to the ''Session Keys'' section on the Developers page.
Session Keys in the UX are broken down into two types. Under the hood, both have the same access rights, however each is stored in a separate manner:
- Developer Session Keys: private keys of these session keys are never stored in in the client nor server. Common use case for this is to register the session key via UX and then use the private key to sign requests in your trading scripts.
- Device Session Keys: created when a user deposits and trades via the UX. To enable instant deposits and trades, a random session private key is generated, registered and encrypted in the browser's local storage. You can manually revoke device session keys below.
You may revoke both developer and device session keys at any time.
Logging into UI with Session Key
You may use session keys to both access the API and UI.
When logging in with a session key into the UI:
- Import the Session Key into your desired wallet provider (e.g. MetaMask).
- Click on the "connect" button in the top right.
- Choose your wallet provider and make sure the account is the Session Key which you imported in step #1.
- Once you connect, you will see a dropdown menu allowing you to connect as "account" owner or as "session key". Choose the "session key" option.
