curl --request GET \
--url https://api.hevn.finance/dapi/v1/transactions/export \
--header 'Authorization: Bearer <token>'import requests
url = "https://api.hevn.finance/dapi/v1/transactions/export"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.hevn.finance/dapi/v1/transactions/export', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));"<string>"{
"error": {
"code": "invalid_request",
"message": "<string>",
"details": {}
}
}Export transactions, a statement, a confirmation or a receipt
Without kind the filtered transaction list is exported as csv, xlsx or pdf. kind=statement and kind=confirmation need bankId and support pdf or xlsx; kind=receipt needs transactionId and answers pdf.
curl --request GET \
--url https://api.hevn.finance/dapi/v1/transactions/export \
--header 'Authorization: Bearer <token>'import requests
url = "https://api.hevn.finance/dapi/v1/transactions/export"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.hevn.finance/dapi/v1/transactions/export', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));"<string>"{
"error": {
"code": "invalid_request",
"message": "<string>",
"details": {}
}
}Authorizations
Platform access token from POST /auth/token, carrying the platform audience and the developer_key_id of the registration that minted it. It acts as your own account; name a client you created with X-Hevn-Account: cl_…. Every request re-checks that the registration is still active and that the caller's source IP is inside its allowlist. A token is valid only against the server that issued it, so sandbox tokens are refused in production and production tokens in the sandbox.
Headers
The client account to act for, as a cl_… id. Omit it to act as yourself.
"cl_9f2c1ab84d7e4f1fa3c65b0e7d9a2c41"
Query Parameters
csv, xlsx, pdf statement, confirmation, receipt Comma-separated transaction types
Comma-separated statuses
Comma-separated tags
2Response
The rendered file, with a Content-Disposition naming it.
The response is of type file.
Was this page helpful?