Skip to main content
This guide walks you through the two Trade History API endpoints. You’ll query trades for a wallet address and look up a specific transaction by hash.
What you’ll build: Scripts that fetch and display trade history from Bebop.Time required: 5 minutesPrerequisites: None for public wallet lookups. To fetch trades attributed to your own integration, authenticate with your API key.

1. Look up trades for a wallet

Retrieve all trades for a given wallet address. The API returns trades across all Bebop-supported chains in a single response.

Understanding the response

This abridged response shows the fields used by most integrations. See the API reference for the complete historical schema.

Trade types

Filtering by time range

Narrow results to a specific window using start and end parameters.
Timestamps are in nanoseconds, not seconds or milliseconds. For example, 1680303600000000000 corresponds to 2023-03-31T21:00:00Z. Passing a millisecond timestamp will return no results.

Pagination

A single response returns at most 500 trades per chain (the size cap). If nextAvailableTimestamp is not null, repeat the request using that value as your new end parameter:

2. Look up a specific transaction

Retrieve details for a single transaction hash. The API searches across all chains automatically.
The response is a single trade object with the same schema as the items in the /trades array.

Errors