curl --request GET \
--url https://api.hevn.finance/dapi/v1/transactions/summary \
--header 'Authorization: Bearer <token>'import requests
url = "https://api.hevn.finance/dapi/v1/transactions/summary"
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/summary', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"inflowUsd": "500.00",
"inflowCount": 123,
"outflowUsd": "500.00",
"outflowCount": 123,
"pendingInflowUsd": "500.00",
"pendingInflowCount": 123,
"pendingOutflowUsd": "500.00",
"pendingOutflowCount": 123
}{
"error": {
"code": "invalid_request",
"message": "<string>",
"details": {}
}
}Inflow and outflow totals for the same filters
Its own route: an aggregate is never folded into a page.
curl --request GET \
--url https://api.hevn.finance/dapi/v1/transactions/summary \
--header 'Authorization: Bearer <token>'import requests
url = "https://api.hevn.finance/dapi/v1/transactions/summary"
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/summary', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"inflowUsd": "500.00",
"inflowCount": 123,
"outflowUsd": "500.00",
"outflowCount": 123,
"pendingInflowUsd": "500.00",
"pendingInflowCount": 123,
"pendingOutflowUsd": "500.00",
"pendingOutflowCount": 123
}{
"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
Comma-separated transaction types
Comma-separated statuses
Comma-separated tags
2Response
Successful Response
Settled incoming value converted to USD for the selected period.
"500.00"
Number of settled incoming transactions in the selected period.
Settled outgoing value converted to USD for the selected period.
"500.00"
Number of settled outgoing transactions in the selected period.
Pending incoming value converted to USD.
"500.00"
Number of pending incoming transactions.
Pending outgoing value converted to USD.
"500.00"
Number of pending outgoing transactions.
Was this page helpful?