One schema for ledgers, invoices, payments, orders, SKUs and campaigns.
PLATFORM
Every integration runs on the Unify Graph.
One data model, one auth flow, one sync engine, one audit trail. Every Unify Int product shares them, so what you build for one platform works for the next.
SHARED BY EVERY PRODUCT
Six pieces, one platform.
A white-label flow your customers use to connect their systems.
Incremental sync, change detection and signed webhooks.
Request logs, webhook replay, sync history and connection health.
Scoped keys and connections, with a log of every read and write.
Governed tools that let AI agents work with your customers' data.
WHY ONE PLATFORM
Point tools leave the seams to you.
An auth library, an iPaaS, a PIM sync and a reporting pipeline each have their own model. The gaps between them become your backlog.
- Write business logic once.
- 1 model
Write business logic once.
Map to the Unify Graph and every connected platform follows. Platform-specific fields stay available in raw and custom field mappings.
- One place to see and govern it all.
- 1 control plane
One place to see and govern it all.
Keys, connections, agents, logs and alerts live in one dashboard, with one permission model.
- Software and services that agree.
- 1 team
Software and services that agree.
The Technology Center builds on the same platform you run, so nothing is handed over in a format you can't maintain.
Three product families on one graph.
INTEGRATIONS
Integration Platform
Auth, a unified API, sync, webhooks and monitoring for every customer connection.
- Unify Connect
- Unified API
- Unify Sync
- Unify Monitor
FINANCE
Finance
Read ledgers and write invoices, bills and payments back, with approvals and an audit trail.
- Accounting API
- Payments API
- Bank Feeds API
- ERP API
PRODUCT DATA
Product Data
Catalog, inventory, orders and ad spend on the same model as your finance data.
- Catalog/PIM API
- Inventory API
- Orders & Commerce API
- Ads API
Designed to be read by engineers.
REST, cursor pagination, typed errors, idempotent writes, webhooks and MCP. One set of concepts across every product.
api.unifyint.com/v1
Sample dataGET /v1/finance/invoices
curl "https://api.unifyint.com/v1/finance/invoices?status=open&limit=1" \
-H "Authorization: Bearer $UNIFY_API_KEY" \
-H "Unify-Connection-Id: conn_qbo_8f2k1"POST /v1/finance/invoices
curl -X POST "https://api.unifyint.com/v1/finance/invoices" \
-H "Authorization: Bearer $UNIFY_API_KEY" \
-H "Unify-Connection-Id: conn_xro_3m9d7" \
-H "Idempotency-Key: 7d1f0c2e-invoice-1048" \
-H "Content-Type: application/json" \
-d '{
"customer_id": "cus_01JC8P9X4R",
"issue_date": "2026-11-01",
"due_date": "2026-12-01",
"currency": "USD",
"line_items": [
{ "description": "Install service", "quantity": "1", "unit_amount": "450.00", "account_id": "acc_01JC7Z1H2B" }
]
}'Unify-Signature: t=1761998400,v1=…
{
"id": "evt_01JC9A3T6P",
"type": "invoice.updated",
"created_at": "2026-11-01T09:20:00Z",
"connection_id": "conn_nts_5q2w4",
"platform": "netsuite",
"data": {
"id": "inv_01JC8Q2K7M",
"status": "paid",
"amount_due": "0.00"
},
"changed_fields": [
"status",
"amount_due"
]
}Tools an agent sees for one connection
{
"tools": [
{
"name": "finance.list_invoices",
"access": "read"
},
{
"name": "finance.create_bill",
"access": "write",
"requires_approval": true
},
{
"name": "commerce.get_order",
"access": "read"
}
],
"policy": {
"max_write_amount": "5000.00",
"audit": "on"
}
}SECURITY
Built for financial data from the first commit.
Encrypted everywhere.
TLS in transit, AES-256 at rest, tokens in a separate vault.
Scoped access.
API keys, connections and agents get only the objects and actions you grant.
Full audit trail.
Every read and write is logged with who, what and when.
Pass-through mode.
Keep sensitive objects out of storage entirely.
Responsible disclosure.
A published policy and a security contact.
Current compliance status is on our Trust page.
Visit the Trust centerPlatform questions.
What is the Unify Graph?
The shared data model under every Unify Int product. Each connected platform is mapped to the same objects, such as Invoice, Payment, Order and SKU, and those objects link to each other.
Can I still reach platform-specific data?
Yes. Every object carries a raw field with the source record, custom fields can be mapped into the model, and passthrough requests call native endpoints with Unify auth and logging.
Do I need every product?
No. Start with one category API. Others share the same auth, keys and connections when you add them.
Is the platform self-serve?
It's built to be. During the developer preview, sandbox access and production keys are issued after a short call, so we can support every early team properly. The Technology Center is there when you want more help.