Skip to main content
GET
/
api
/
v1
/
transactions
/
export
cURL
curl -sS -X GET "$FLUIDE_BASE_URL/api/v1/transactions/export" \
  -H "Authorization: Bearer $FLUIDE_ACCESS_TOKEN" \
  -H "X-Fluide-Api-Key: $FLUIDE_API_KEY" \
  -H "X-Fluide-Client-Id: fluide-developer"
{
  "success": true,
  "message": "Operation completed successfully",
  "data": {}
}

Authorizations

​
Authorization
string
header
required

Access token JWT. Use as Authorization: Bearer . In the API playground, paste the JWT only.

​
X-Fluide-Api-Key
string
header
default:fl_dev_your_key
required

Developer API key (fl_dev_...). Required on every API call with a machine access token.

​
X-Fluide-Client-Id
string
header
default:fluide-developer
required

First-party client audience. Must match the fluide_client_id claim on the JWT. Use fluide-developer for Connect.

Headers

​
authorization
string
required

Query Parameters

​
q
string

Free-text search (endpoint-specific)

Maximum string length: 200
​
page
number
default:1

Page number (1-indexed)

Required range: x >= 1
​
limit
number
default:5000

Max rows to export (server-capped)

Required range: 1 <= x <= 10000
​
sort
string

Sort in the format field:direction (allocatedAt:desc)

Maximum string length: 50
​
startDate
string

Filter allocatedAt on/after this date (ISO)

​
endDate
string

Filter allocatedAt on/before this date (ISO)

​
documentType
enum<string>

Document type filter

Available options:
INVOICE,
BILL
​
paymentSource
string

Payment source filter

Maximum string length: 32
​
currency
string

Currency filter (ISO)

Maximum string length: 3
​
format
enum<string>
default:csv

Export format

Available options:
csv,
xlsx,
pdf

Response

Transaction export file

​
success
boolean
required

Whether the request succeeded

Example:

true

​
message
string
required

Human-readable outcome message (localized when i18n is configured)

Example:

"Operation completed successfully"

​
data
object

Endpoint-specific payload