Walletguide
DevelopersAPIReferencedata

CashFlowTimeSeries

Whole-wallet figures need the permissions listed without assets:read; scoping the request with assetIds makes it a per-asset breakdown, which needs…

POST
/wallets/{walletId}/data/cashFlowTimeSeries

Authorization

bearerAuth
headerAuthorization<token>

A Walletguide API key (wg_…) or an OAuth bearer token. Paste the value only. Create a key under Wallet settings → API keys.

Path Parameters

walletId*string

The wallet id (row uuid)

Formatuuid

Request Body

application/json
  1. body
period?|

Window to bound the series to. Omit for full history.

dateInterval?string

Bucket granularity (default 'month').

Value in"month""day"
assetIds?array<string>

Scope to these asset uuids; omit for whole-wallet.

categoryIds?array<string>

Scope to these category uuids; omit for all categories.

Response Body

cashFlowTimeSeries result

application/json
  1. response
series*
Example Request
curl -X POST 'https://api.walletguide.com/wallets/497f6eca-6276-4993-bfeb-53cbbbba6f08/data/cashFlowTimeSeries' \  -H 'Content-Type: application/json' \  -d '{}'
Example Response
{  "series": {    "property1": [      {        "period": "string",        "value": 0      }    ],    "property2": [      {        "period": "string",        "value": 0      }    ]  }}

CashFlowByCategory

Whole-wallet figures need the permissions listed without assets:read; scoping the request with assetIds makes it a per-asset breakdown, which needs…

CategoryBreakdown

Whole-wallet figures need the permissions listed without assets:read; scoping the request with assetIds makes it a per-asset breakdown, which needs…