Custom fields.
Map your customers' custom fields into the model, per connection, without code changes.
NEWUnify Agents (MCP): governed AI access to finance data. Early access.See Unify Agents
BANK FEEDS API
Card issuers, neobanks and spend platforms use the Unify Bank Feeds API to create feed accounts and send transactions into QuickBooks Online, Xero and more, ready to reconcile.
POST /v1/finance/bank-feeds/bfa_01JC5K8N3W/transactions
curl -X POST "https://api.unifyint.com/v1/finance/bank-feeds/bfa_01JC5K8N3W/transactions" \
-H "Authorization: Bearer $UNIFY_API_KEY" \
-H "Unify-Connection-Id: conn_xro_3m9d7" \
-H "Content-Type: application/json" \
-d '{
"transactions": [
{ "id": "txn_card_88213", "posted_date": "2026-10-31", "amount": "-64.20",
"description": "Blue Bottle Coffee", "category": "Meals", "memo": "Team offsite" }
]
}'202 Accepted
{
"feed_account_id": "bfa_01JC5K8N3W",
"platform": "xero",
"accepted": 1,
"duplicates": 0,
"status": "queued"
}OBJECTS
Read and write status comes from coverage data for each platform on this API. Write shows only where write-back is confirmed.
On 6 of 10 platforms; readable on 2.
On 6 of 10 platforms; readable on 2.
On 6 of 10 platforms; readable on 2.
On 6 of 10 platforms; readable on 2.
On 6 of 10 platforms; readable on 2.
On 6 of 10 platforms; readable on 2.
On 6 of 10 platforms.
On 6 of 10 platforms.
On 5 of 10 platforms; readable on 2.
On 5 of 10 platforms; readable on 2.
On 5 of 10 platforms; readable on 2.
On 5 of 10 platforms; readable on 2.
Also in the data model: Balance, Account Mapping.
NO LOWEST COMMON DENOMINATOR
Map your customers' custom fields into the model, per connection, without code changes.
Every object carries the platform's original record in raw, for the edge cases.
Call any native endpoint with Unify auth, rate limiting and logging.
Subsidiaries, locations and currencies are fields, not afterthoughts.
Merchant name, category and memo sent in each ledger's fields.
Transaction ids are idempotent, so retries never double-post.
Missed days are flagged and backfilled.
10 platforms live or in beta across 9 categories.
Live, beta and roadmap status for every object below.
| Platform | Read | Write | Webhooks | Bank feeds | Catalog/PIM |
|---|---|---|---|---|---|
| Plaid | Beta | Not supported | Beta | Beta | Not supported |
| QuickBooks Online | Beta | On the roadmap | Beta | On the roadmap | Not supported |
| Xero | Beta | On the roadmap | Beta | On the roadmap | Not supported |
| FreshBooks | On the roadmap | On the roadmap | On the roadmap | On the roadmap | Not supported |
| Mastercard Open Finance | On the roadmap | Not supported | On the roadmap | On the roadmap | Not supported |
| MX | On the roadmap | Not supported | On the roadmap | On the roadmap | Not supported |
| MYOB | On the roadmap | On the roadmap | Not supported | On the roadmap | Not supported |
| Sage Accounting | On the roadmap | On the roadmap | Not supported | On the roadmap | Not supported |
Showing 8 of 10 platforms.
No. A bank feed pushes transactions into accounting software. Bank account data reads balances and transactions from banks. The Bank Feeds API does the first and reads the second from data providers.
Some do. Where a ledger runs a partner program for feeds, the Technology Center can help with the application and certification steps.
It depends on the ledger; typical limits are listed on each integration page.
Yes. Sandbox access is free for early-access teams and design partners: demo companies on QuickBooks Online, Xero and Shopify, and test credentials for other platforms where the vendor offers them. Request it on the Get started page.
Yes: through raw, custom field mapping, or passthrough requests to native endpoints.
Get started
Request sandbox access, or book 30 minutes with an engineer to map your integrations.
Free sandbox access. No credit card. Reply within one business day.