How to view API transaction records on Bybit? Is there a limit on the number of transactions?

Bybit's API allows users to retrieve transaction records using the /v2/private/wallet/transaction-log endpoint, with limits on rate and historical data access.

May 19, 2025 at 07:07 am

Bybit is a popular cryptocurrency exchange that provides robust API services for traders who want to automate their trading strategies or manage their portfolios programmatically. One of the key features that users often need to access through the API is the transaction records. This article will guide you through the process of viewing API transaction records on Bybit, and discuss any limits that may be in place on the number of transactions you can retrieve.

Understanding Bybit's API

Before diving into the specifics of retrieving transaction records, it's essential to understand the basics of Bybit's API. Bybit's API allows users to interact with the platform programmatically. This includes executing trades, managing orders, and fetching various data such as transaction records. The API is designed to be secure and efficient, ensuring that users can manage their accounts effectively.

Accessing the API

To start using Bybit's API, you need to set up an API key. Here are the steps to do so:

• Log into your Bybit account.
• Navigate to the API Management section. This can usually be found under the account settings or user profile section.
• Create a new API key. You will need to provide a name for the key and set permissions according to your needs.
• Save the API key and secret. These will be used to authenticate your API requests.

Retrieving Transaction Records

Once you have set up your API key, you can start making requests to retrieve transaction records. Bybit's API provides endpoints specifically designed for fetching transaction data. The endpoint you will use is /v2/private/wallet/transaction-log.

Here's how to make a request to this endpoint:

• Prepare your request. You will need to include your API key and secret in the request headers to authenticate it.
• Specify the parameters. You can filter the transaction records by specifying parameters such as currency, start_date, end_date, and exec_type. These parameters help you narrow down the results to the transactions you are interested in.
• Send the request. Use a tool like Postman or write a script in your preferred programming language to send the request to Bybit's API server.

Here's an example of what the request might look like in Python using the requests library:

import requests
import time
api_key = 'your_api_key'
api_secret = 'your_api_secret'
base_url = 'https://api.bybit.com'
endpoint = '/v2/private/wallet/transaction-log'
Prepare the parameters
params = {
'currency': 'BTC',
'start_date': '2023-01-01',
'end_date': '2023-01-31',
'exec_type': 'Deposit'
}
Generate the timestamp
timestamp = int(time.time() * 1000)
Prepare the headers
headers = {
'Content-Type': 'application/json',
'api_key': api_key,
'timestamp': str(timestamp),
'sign': generate_signature(api_secret, timestamp, params)  # You need to implement the generate_signature function
}
Send the request
response = requests.get(base_url + endpoint, headers=headers, params=params)
Process the response
if response.status_code == 200:
print(response.json())
else:
print(f"Error: {response.status_code}")
Understanding the Response
When you successfully retrieve transaction records, Bybit's API will return a JSON response containing the requested data. The response will include fields such as id, time, currency, amount, type, and status. It's important to parse this data correctly to make sense of your transaction history.
Here's an example of what the response might look like:
{
"ret_code": 0,
 "ret_msg": "OK",
 "ext_code": "",
 "ext_info": "",
 "result": {
"data": [
  {
    "id": "123456",
    "time": "2023-01-05T12:34:56Z",
    "currency": "BTC",
    "amount": "0.1",
    "type": "Deposit",
    "status": "Success"
  },
  {
    "id": "123457",
    "time": "2023-01-10T12:34:56Z",
    "currency": "BTC",
    "amount": "0.2",
    "type": "Withdrawal",
    "status": "Success"
  }
]
}
}

Limits on Transaction Records

Bybit imposes certain limits on the number of transactions you can retrieve through the API. These limits are in place to prevent abuse and ensure fair usage of the platform's resources. Here are some key points to keep in mind:

• Rate Limits: Bybit has rate limits on API requests. For example, you might be limited to a certain number of requests per minute or per day. Exceeding these limits can result in your API key being temporarily blocked.
• Pagination: When retrieving transaction records, Bybit uses pagination to manage large datasets. You can specify the limit parameter to control the number of records returned in each response, and use the page parameter to navigate through multiple pages of results.
• Historical Data: There might be limits on how far back you can retrieve transaction records. Bybit typically allows you to fetch data for a certain number of days or months in the past.

To manage these limits effectively, you should:

• Monitor your API usage. Keep track of how many requests you are making and ensure you stay within the rate limits.
• Implement pagination. Use the limit and page parameters to retrieve data in manageable chunks.
• Plan your data retrieval. If you need to fetch a large amount of historical data, plan your requests carefully to avoid hitting the limits.

Handling Errors

When working with Bybit's API, you may encounter errors. Common errors include authentication failures, rate limit exceeded, and invalid parameters. Here's how to handle these errors:

• Authentication Errors: If you receive an authentication error, double-check your API key and secret. Ensure they are correctly included in the request headers.
• Rate Limit Errors: If you exceed the rate limit, wait for a period before retrying your request. Implement a delay in your code to prevent hitting the rate limit repeatedly.
• Invalid Parameters: If the API returns an error due to invalid parameters, review your request and ensure all parameters are correctly formatted and within the acceptable range.

FAQs

Q: Can I retrieve transaction records for multiple currencies at once using Bybit's API?

A: No, Bybit's API requires you to specify a single currency when retrieving transaction records. If you need records for multiple currencies, you will need to make separate API requests for each currency.

Q: How can I ensure the security of my API key when retrieving transaction records?

A: To ensure the security of your API key, never share it with anyone, and use it only in secure environments. Additionally, consider using Bybit's IP whitelist feature to restrict API access to specific IP addresses.

Q: Is there a way to automate the retrieval of transaction records on a schedule?

A: Yes, you can automate the retrieval of transaction records by writing a script that makes API requests on a schedule. Use a scheduling tool like cron jobs on Unix-based systems or Task Scheduler on Windows to run your script at regular intervals.

Q: What should I do if I encounter a 429 Too Many Requests error?

A: If you encounter a 429 error, it means you have exceeded Bybit's rate limits. Wait for a period before retrying your request, and consider implementing a delay in your code to prevent hitting the rate limit repeatedly.