Retrieve filtered records from a Blnk Core instance via JSON filters through Blnk Cloud.
curl -X POST 'https://api.cloud.blnkfinance.com/transactions/filter?instance_id=YOUR_INSTANCE_ID&page=1&pageSize=20' \
-H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
-H 'Content-Type: application/json' \
-d '{
"filters": [
{ "field": "status", "operator": "eq", "value": "APPLIED" },
{ "field": "currency", "operator": "in", "values": ["USD", "EUR"] }
]
}'
{
"data": [
{
"transaction_id": "txn_c4e70eb8-e4d6-4e04-a2e2-92a43b969e0c",
"amount": 100.50,
"currency": "USD",
"status": "APPLIED",
"created_at": "2025-01-15T10:00:00.000000000Z"
}
],
"total": 12,
"stats": {},
"total_is_estimate": false,
"total_source": "exact"
}
The Filters API lets you retrieve filtered records from a Blnk Core instance through Blnk Cloud. Send a POST request with a JSON filter body to query instance Postgres directly.Documentation Index
Fetch the complete documentation index at: https://docs.blnkfinance.com/llms.txt
Use this file to discover all available pages before exploring further.
/transactions/filter), not under /data/ or /proxy/. For a step-by-step guide, see Filtering data.curl -X POST 'https://api.cloud.blnkfinance.com/transactions/filter?instance_id=YOUR_INSTANCE_ID&page=1&pageSize=20' \
-H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
-H 'Content-Type: application/json' \
-d '{
"filters": [
{ "field": "status", "operator": "eq", "value": "APPLIED" },
{ "field": "currency", "operator": "in", "values": ["USD", "EUR"] }
]
}'
data:read scope. Create credentials with the data:read scope in API keys or OAuth clients.field and operator, and optionally value or values.Examples:[{"field": "status", "operator": "eq", "value": "APPLIED"}] — exact match[{"field": "currency", "operator": "in", "values": ["USD", "EUR"]}] — multiple values[{"field": "created_at", "operator": "between", "values": ["2025-01-01T00:00:00Z", "2025-01-31T23:59:59Z"]}]https://api.cloud.blnkfinance.com.
| Method | Path | Default pageSize |
|---|---|---|
| POST | /ledger/filter | 30 |
| POST | /balances/filter | 20 |
| POST | /transactions/filter | 20 |
| POST | /identities/filter | 20 |
| POST | /reconciliation/filter | 20 |
/ledger/filter (singular), not /ledgers/filter.{
"data": [
{
"transaction_id": "txn_c4e70eb8-e4d6-4e04-a2e2-92a43b969e0c",
"amount": 100.50,
"currency": "USD",
"status": "APPLIED",
"created_at": "2025-01-15T10:00:00.000000000Z"
}
],
"total": 12,
"stats": {},
"total_is_estimate": false,
"total_source": "exact"
}
true, the total value is an estimate rather than an exact count."exact" or "estimate").{ "filters": [...] } in the body with pagination via query parameters.This differs from the self-hosted Core Filter API documented in Search via DB, which uses limit, offset, sort_by, and include_count in the body and returns total_count.Was this page helpful?
curl -X POST 'https://api.cloud.blnkfinance.com/transactions/filter?instance_id=YOUR_INSTANCE_ID&page=1&pageSize=20' \
-H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
-H 'Content-Type: application/json' \
-d '{
"filters": [
{ "field": "status", "operator": "eq", "value": "APPLIED" },
{ "field": "currency", "operator": "in", "values": ["USD", "EUR"] }
]
}'
{
"data": [
{
"transaction_id": "txn_c4e70eb8-e4d6-4e04-a2e2-92a43b969e0c",
"amount": 100.50,
"currency": "USD",
"status": "APPLIED",
"created_at": "2025-01-15T10:00:00.000000000Z"
}
],
"total": 12,
"stats": {},
"total_is_estimate": false,
"total_source": "exact"
}