# Bybit
**Important Note: API keys with Bybit expire 90 DAYS after being created**. Be sure to set reminders to refresh these keys prior to this date in order to prevent any data collection gaps.
**Step One:** Log in to your Bybit account at
**Step Two:** After signing in, select your ***profile icon*** in the top right corner, then select ***API*** from the dropdown.
**Step Three:** Select the “Create New Key” button.
**Step Four (a):** Select the API Key usage parameters.
Be sure to enable "API Transactions" and give the API key a label. In our example we chose to make it “How To Guide”. We recommend making the label as descriptive as possible to reflect the use case of the specific API.
Then you should verify that "Read-Only" and "No IP restrictions" are the options selected next. Ensure that all functions relating to trading, transfers, and withdrawals are disabled. This should be the case by default, however it is important to double-check at this stage as the Hash Data tool will deny the API key if any trading functions are enabled.
**Step Four (b):** Select the API Key permissions.
Scrolling down, you will see the full list of permissions - by default, Bybit will have this blank. Ensure that all of these permissions are **enabled** *(excluding Withdrawal)*, as otherwise the Hash Data tool will not be able to obtain complete information from the account.
Once these are selected as shown below, hit "Submit" and enter the 2FA authenticator codes when prompted.
**Step Five:** Record your generated keys.
Be sure to record your "API Secret" Key in a secure location, as this key will be permanently hidden once the page is refreshed or you hit the "Understood" button.
**Step Six:** Enter your API keys into the Hash Data tool
Log into the Client Portal of the Hash Data tool, then navigate down to **Exchange Accounts** (1), selected **Add Exchange** (2), then enter your keys where prompted (3). As reference, the "API Key" from Bybit is the "[Public Key](#user-content-fn-1)[^1]" in the Hash Data tool, and the "API Secret" refers to the Secret Key.
**Step Seven:** Click "Test Keys" and let that complete.
If the test sends an error in response, please re-review the information entered and the permissions associated with the API key. The software has a number of checks in place to prevent users from uploading keys with "Edit" capabilities, so this is the most common source of errors.
Once the keys are tested and no errors are noted, click "Submit".
**Congratulation - the Hash Data tool is now able to read your exchange account!**
If you are looking for information on how to process information from your exchange account and begin running reports from this balance, please proceed to the **User Guide**!
For any questions, please reach out to for additional assistance.
[^1]: The key visible to everyone
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://hash-data.gitbook.io/exchange-api-guide/bybit.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.