List the fund movements of a budget

The budget's funds history: who moved its funds in or out, how much, from or to where
and why. Newest first (created_at desc, then id desc). Closed budgets still return
their history.

Access

  • Admin / budgets_manage users and Cardda staff.
  • Members of the budget: its manager ("Encargado"), a co-manager or a participant,
    explicit or by holding one of its non-canceled cards.

Someone who sees the budget only because it's open to the company
(access: company) gets 401. A budget outside the caller's scope returns
404 Not Found.

Pagination

_start/_end paginate (25 rows by default), with Content-Range and
X-Total-Count in the response. There is no _field/_order sorting.

What it holds

The history starts when this endpoint was released; older movements are not
backfilled. Assigning or unassigning loaded prepaid cards, period renewals and the
budget's creation are not recorded, so the rows don't add up to
allocated_amount_cents.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
uuid
required

The UUID of the balance group (budget).

Query Params
integer
≥ 0

If all the transactions where in an array, this would represent the index of the first item returned in the response

integer
≥ 0

If all the transactions where in an array, this would represent the index of the last item returned in the response

Headers
uuid
required

UUID of the company on whose behalf the request is made. Required for every Finance endpoint.
See The company-id header for details on how to obtain
a value for this header and the error responses to expect when it is missing or invalid.

Responses

401

Unauthorized - missing or invalid authentication token, or a caller who sees the
budget only because it's open to the company (not an admin nor a member of it).

Language
Credentials
Bearer
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json