Skip to main content
This guide runs the full pipeline once, so the claim on the homepage (“Cherry categorizes, books, and folds pushed transactions into your statements”) becomes something you’ve watched happen. You will:
  1. Create a manual bank account.
  2. Push one transaction into it.
  3. Read the transaction back with its categorization.
  4. Read the resulting P&L line.
You need a write API key. See Authentication if you don’t have one yet.

1. Create a bank account

The response confirms the account and whether it was auto-mapped to a ledger account. Re-posting the same institution is safe: externalId keeps it idempotent.

2. Push a transaction

Send one Figma subscription charge on that account.
Amount is 49.99, not -49.99: positive is money out. See Conventions. Re-running this exact call is a no-op. txn-e2e-001 is your stable id, so Cherry will match and dedupe.

3. Read it back, categorized

Categorization runs asynchronously and usually completes within a minute or two. Poll the transaction until category is populated.
If the category is wrong, PATCH it. Cherry remembers the correction for future transactions from the same merchant:

4. See it on the P&L

The same categorization drives your statements. Pull August’s profit and loss:
The Software & Subscriptions line under expenses includes your $49.99 charge. The figures here come from the same generator the Cherry app uses, so what you see in the API matches the product exactly.

What you just did

  • Cherry took a raw bank transaction and mapped it to a ledger account (6110).
  • It booked a journal entry against the checking account you created in step 1.
  • The entry rolled into the P&L for August without any extra call.

Where to go next

  • Push your own transactions covers batching, large imports, and the full idempotency rules.
  • Connect an agent over MCP exposes the same pipeline as tools for Claude or ChatGPT.
  • The API Reference tab has every endpoint used above with the full request and response schemas.