Vezmo App

Accounts API · Accounts API

Transactions

Requires transactions.read. Every line booked on your spendable balances, newest first: money in, transfers, fees, returns and corrections. One transaction is one line on one balance.

List transactions — GET /transactions

  • accountId — the balance an account feeds (acct_…). A currency that isn't that balance's is 400.
  • currency, direction (in | out).
  • type — incoming, transfer, return, fee, adjustment.
  • status — pending (a transfer still on its way), posted, returned (a transfer refused or sent back; its return is its own line).
  • postedFrom, postedTo, createdFrom, createdTo — RFC 3339 with a zone.
  • amountMin, amountMax — minor units.
  • transferId — tr_…; one that isn't yours gives an empty page.
  • recipientId, reference — not available yet: 400 unsupported_filter.
Request
curl "https://api.vezmo.com/api/v1/transactions?currency=USD&direction=in&postedFrom=2026-10-01T00:00:00Z&limit=50" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Vezmo-Version: 2026-11-14"
One entry of data[]
{
  "id": "txn_cm3k9q2xv0001",
  "type": "incoming",
  "direction": "in",
  "amount": 124900,
  "currency": "USD",
  "fee": 100,
  "status": "posted",
  "description": "Money in from Harbor & Co.",
  "counterparty": { "name": "Harbor & Co.", "maskedAccount": null, "country": "US" },
  "reference": null,
  "transferId": null,
  "postedAt": "2026-10-14T16:02:11.000Z"
}
  • description — in our words, never an internal id; internal corrections read “Adjustment”.
  • fee — the fee taken on this line, if any. counterparty — the payer or the recipient, account masked.

status with a very large number of transfers in that state answers 400 unsupported_filter: filter by transferId instead.

Get one transaction — GET /transactions/{id}

The same object. “No such transaction.” (404) for an id that isn't yours.

Keeping a ledger in step

Poll with postedFrom a little before your last run and upsert by id, or listen to transaction.posted.

Node.js
// Keep a ledger in step: poll with an overlap, dedupe by id (or listen to transaction.posted).
async function pull(since) {
  let after;
  do {
    const q = new URLSearchParams({ postedFrom: since, limit: "100", ...(after ? { startingAfter: after } : {}) });
    const res = await fetch(`https://api.vezmo.com/api/v1/transactions?${q}`, {
      headers: { Authorization: `Bearer ${await accessToken()}`, "Vezmo-Version": "2026-11-14" },
    });
    const body = await res.json();
    for (const t of body.data) await upsertById(t);
    after = body.meta.hasMore ? body.meta.nextCursor : undefined;
  } while (after);
}