Linked objects.
An order knows its SKUs, its payout and the journal entry it posted.
UNIFY GRAPH
One data model for finance and product data.
The Unify Graph maps ledgers, invoices, payments, orders, SKUs and campaigns from every connected platform to one schema, and links them to each other.
How the objects connect.
Finance · linked to Company
- Account
- Invoice
- Bill
- Payment
- Journal Entry
- Customer
- Vendor
Product · linked to Company
- Product
- SKU
- Inventory Level
- Order
- Fulfillment
- Payout
Ads · linked to Company
- Campaign
- Insight
- Payment settles Invoice
- Order contains SKU
- Payout posts to Journal Entry
- Campaign drives Order
Why one graph beats many schemas.
Stable ids.
Unify ids never change;
remote_idkeeps the platform's own id.Raw always available.
The source record rides along in
raw.Versioned schema.
Additive changes ship continuously; breaking changes get a dated version and a migration window.
HOW IT WORKS
Connect, map, use.
Connect.
A customer connects a platform with Unify Connect.
Map.
We map its records to Unify Graph objects and custom fields you choose.
Use.
You read, write and subscribe through one API, and agents call the same objects as tools.
Unify Graph questions.
Is the Unify Graph a database we query?
It's a data model exposed through the API. Sync-and-store objects are served from our encrypted store; pass-through objects are fetched live.
Can we extend it?
Yes, with custom field mappings per connection and custom objects built by the Technology Center.
How do you version it?
Dated API versions; your account pins one, and we announce changes by email with migration notes.
Can we export it to our warehouse?
Yes, via API and webhooks today; managed warehouse export is on the roadmap.