List every movement in one timeline
One feed for everything that moved value for your customers: the transfers you created through this API, and the on-chain deposits credited into custody. You no longer have to stitch two listings together and guess the order between them.
Ordered newest first. Each row carries a type (transfer or deposit), so you can branch without a second lookup, and the id is the id of the underlying resource - use it to fetch the full record.
Paginated with the standard opaque cursor. The cursor spans both sources at once: it is not one cursor per source, so a busy day on one side can never hide rows from the other.
Card transactions are not in this feed. They are read per card at GET /cards/{card_id}/transactions.
Request
- Base URLhttps://developers.ozav.io/v2
- Auth
- API key in header X-API-Key
- or HTTP bearer
Query parameters
Page size.
Opaque cursor returned as next_cursor on the previous page.
Filter to a single customer by its opaque ozav_cus_ id. Applies to both sources: transfers created for that customer, and the deposits credited to it.
An id that does not exist, or belongs to another organization or another environment, returns an empty page rather than 404 - the same behaviour as GET /transfers, so a filter never tells you whether an id exists somewhere you cannot see.
Response
A page of movements, newest first.
Example response
{
"data": [
{
"amount": "1250.00"
}
]
}Changes
No recorded changes to this operation across all 1 revision of this API.