Skip to main content
Breadbox automatically pulls transactions from your connected bank accounts on a scheduled sync. Each transaction is stored in your PostgreSQL database and exposed through the admin dashboard, REST API, and MCP server.

​
How transactions are synced

When you connect a bank account, Breadbox performs an initial sync that pulls your full available transaction history. After that, syncs run on the schedule you configure (every 4, 8, 12, or 24 hours) and also fire immediately whenever your bank pushes a webhook notification. Each sync fetches only the changes since the last run — new transactions, modifications to pending transactions, and removals. Breadbox processes these three lists atomically so your database stays consistent. You can trigger a manual sync at any time from the admin dashboard under Connections, or by calling POST /api/v1/sync from the REST API.

​
Amount convention

Breadbox passes Plaid’s native sign convention through without modification: For example, a 12.50coffeepurchaseisstoredas‘amount=12.50‘.A12.50 coffee purchase is stored as `amount = 12.50`. A 1,000 paycheck deposit is stored as amount = -1000.00.
Never sum amounts across different currencies. Always check iso_currency_code before aggregating, and treat each currency separately.

​
Key transaction fields

Every transaction record includes the following fields: The is what AI agents and MCP tools use when referring to transactions. You can pass either id or short_id to any API endpoint or MCP tool that accepts a transaction identifier.

​
Pending vs. posted transactions

A transaction starts as pending when the bank reports it but it has not yet settled. Pending transactions may change or be cancelled before they post. When a pending transaction settles, the bank may issue a new transaction ID for the posted version. Breadbox links the posted record back to the pending one and soft-deletes the pending row automatically, so you see only one record per transaction. Pending transactions are included in API responses and dashboard views by default. Use the pending=false query parameter to filter to posted transactions only.

​
Browsing transactions in the dashboard

Navigate to Transactions in the admin dashboard sidebar to browse, search, and filter your transaction history. From there you can:
  • Filter by account, date range, category, amount, or keyword
  • Click any transaction to view its full details and activity timeline
  • Manually override a transaction’s category
  • Add tags and comments

​
Querying via API and MCP

For programmatic access, Breadbox offers two interfaces:
  • REST API — Use GET /api/v1/transactions with query parameters to filter (date, account, user, category, amount, search), sort, paginate, and filter by tags (tags= / any_tag=). See Transactions API for the full parameter list and Tags API for attaching and detaching tags.
  • MCP server — AI agents connect to Breadbox’s MCP server and use tools like query_transactions, count_transactions, and update_transactions to query, categorize, tag, and summarize in natural-language workflows. See MCP overview for setup and MCP Reference for the full tool list.

​
Soft deletes

When your bank reports that a transaction has been removed (for example, a declined charge or a reissued pending transaction), Breadbox sets a deleted_at timestamp on the row rather than erasing it. The transaction disappears from normal API responses and dashboard views, but the record is never hard-deleted from your database. This preserves history and keeps any prior agent references consistent.
Last modified on June 25, 2026