Introducing New List API Endpoints for Payments and Transactions

We’ve introduced new List API endpoints that allow developers to retrieve historical data for checkout payments, deposit requests, and ticker-based transactions directly through the BlockBee API.

These endpoints provide a practical way to access payment history programmatically, making it easier to build reporting tools, monitoring systems, financial workflows, and internal integrations.

All three endpoints support pagination and timestamp filtering, allowing users to retrieve only the data they need in a structured and efficient way.

What’s New?

We’ve added three new API endpoints designed to retrieve historical transaction and payment data:

• List Checkout Payments
• List Deposit Requests
• List API Transactions by Ticker

Each endpoint returns paginated results and detailed response fields to help developers work with large datasets more efficiently.

List Checkout Payments

The Checkout Payments List endpoint allows users to retrieve a paginated history of checkout payment requests for a profile.

This endpoint is useful for tracking payment activity, reviewing past requests, or building custom reporting tools around checkout flows.

Key Features

• Retrieve checkout payment history programmatically
• Filter results using from and to Unix timestamps
• Filter by payment status such as waiting, paid, pending, partial, and expired
• Use pagination with page and per_page

The response includes fields such as num_pages and a payments array containing information like source, token, value, payment_list, and is_paid.

List Deposit Requests

The Deposit Requests List endpoint allows users to retrieve a paginated history of deposit requests together with their associated received payments.

This is especially useful for integrations that rely on deposit flows and need visibility into which requests have received funds.

Key Features

• Retrieve deposit request history programmatically
• Filter results using from and to Unix timestamps
• Filter by status such as with_payments and without_payments
• Use pagination with page and per_page

The response includes fields such as num_pages and a deposits array with values like token, value_fiat, currency, and a nested payment_list containing transaction details such as txid, value, coin, and timestamp.

List API Transactions by Ticker

The Ticker Transactions List endpoint allows users to paginate through transactions associated with a specific cryptocurrency ticker.

This makes it easier to retrieve data for customized payment or deposit integrations tied to a particular blockchain or token.

Key Features

• Retrieve transactions related to a specific ticker
• Use the ticker directly in the endpoint path
• Filter transactions using from and to Unix timestamps
• Use pagination with page and per_page

The response includes fields such as num_pages and a transactions array containing data like uuid, address_in, address_out, txid_in, fiat_forwarded, fee_deducted, blockchain_fee, and result.

Built for Reporting and Automation

These new List endpoints make it easier to automate payment tracking and integrate BlockBee data into external systems.

Common use cases include reporting dashboards, transaction monitoring, reconciliation workflows, internal analytics, and financial record synchronization.

By returning structured and paginated data, we help keep integrations efficient and scalable even when handling larger volumes of payment activity.

Get Started

Developers can start using these endpoints immediately through the BlockBee API.

All three endpoints use API key authentication and support optional filtering parameters such as timestamps, pagination, and status values depending on the endpoint.

With these additions, we continue to make payment and transaction data more accessible for developers building advanced crypto payment workflows.