Retrieve Data

What It Does

Use read endpoints to retrieve ingested records for your API key.

Send logical table names such as clients, disbursements, payments, or operations; the API scopes the request to your data.

Authorization: Bearer YOUR_API_KEY

List Records

GET /api/tables/:table

Example:

GET /api/tables/payments?limit=25&sort_by=payment_date&sort_order=desc
Authorization: Bearer YOUR_API_KEY

Response:

{
  "data": [
    {
      "payment_id": "PAY-2024-001",
      "disbursement_id": "DSB-2024-001",
      "amount": 250,
      "currency": "USD"
    }
  ],
  "pagination": {
    "limit": 25,
    "has_more": false
  }
}

Query Parameters

ParameterNotes
limitRows per page. Defaults to 50.
cursorCursor from pagination.next_cursor to retrieve next page.
sort_byColumn to sort on. Defaults to created_at; asset_status and disbursement_status default to on_date.
sort_orderasc or desc. Defaults to desc.
include_countSend true to include total and total_pages.
date_fieldColumn used by start_date and end_date. Required when either date filter is present.
start_dateInclusive lower date bound for date_field.
end_dateInclusive upper date bound for date_field.
searchPartial match across searchable ID/status columns for that table.

Get One Record

GET /api/tables/:table/:id

Example:

GET /api/tables/disbursements/DSB-2024-001
Authorization: Bearer YOUR_API_KEY

Response:

{
  "data": {
    "disbursement_id": "DSB-2024-001",
    "client_id": "BR-2024-001",
    "amount": 10000,
    "currency": "USD"
  }
}

The :id value uses the table primary key:

Allowed Tables

clients, disbursements, payments, operations, purchase_clients,

asset_status, disbursement_status,

write_offs, rebates , extensions , restructures

Errors