APIXX Data
APIXX Data is the canonical, normalized data layer that sits on top of every connector. Instead of pulling raw Shopify orders here and raw NetSuite orders there, you query one canonical 'order' entity with full provenance back to every source row that contributed.
What APIXX Data is
APIXX Data is a managed read store. Flows ingest source rows; the data layer normalizes, deduplicates, and merges them into canonical entities. You query the canonical layer from the dashboard, from the public API, or from BI tools via the read endpoints.
Canonical entities
Out of the box:
- Commerce — customer, contact, account, product, product_variant, order, order_line_item, inventory, shipment, refund.
- Finance — invoice, payment, subscription.
- CRM — lead, opportunity.
- Custom — define your own entities via the schema editor.
IDs & deduplication
Every canonical record has a stable canonical_id (UUID v4) and an external_ids map keyed by source system. When two source rows match on a configurable identity rule (e.g. email + tenant for customers), they merge into one canonical record with both external IDs.
| Field | Type | Description |
|---|---|---|
| canonical_id | uuid | Stable identifier across all sources. |
| external_ids | map<source, id> | { shopify: 'gid://...', netsuite: '12345' } |
| updated_at | timestamp | When canonical record last changed. |
| last_source_update_at | timestamp | When the contributing source row last changed. |
| sources | array | List of source systems contributing fields. |
Schema versioning
The canonical schema is versioned. Additive changes (new optional fields) ship in minor versions and never break consumers. Breaking changes ship in major versions with a 6-month deprecation window. Pin your API clients to a major version via the Accept-Version header.
Mapping Console
When a new source system comes online, the Mapping Console proposes a source → canonical field map using name similarity and sample data. You review, approve, or override each rule.
- Confidence score on every suggested mapping.
- Diff view when re-mapping after a source schema change.
- Versioned — every approved map is immutable; new versions ship as drafts.
- Promote / rollback with one click.
Coverage
The Coverage dashboard is a source × entity heatmap. Cells turn green when at least one flow is actively ingesting that combination. Hover any cell for last-run time, record count, and freshness lag. Use it to spot gaps before they become incidents.
Quality checks
Each entity ships with default checks; you can add custom ones:
- Required-field completeness — % of records with all required fields populated.
- Referential integrity — every order has a valid customer.
- Freshness — newest record is within SLA.
- Range / format — currency codes ISO 4217, emails RFC 5322.
- Drift — distribution of
statusvalues vs. last week.
Provenance & audit
For any field on any canonical record, you can see exactly which source row contributed the value, when, and via which flow run. This is essential for finance and compliance reviews — every number in APIXX Data is traceable to its origin.
Reading data
Browse the canonical store from Data → Live Records, or pull it programmatically via the API. The read API supports cursor pagination, sparse field selection, and incremental updated_since filters for efficient sync into your warehouse.
Retention & trash
Deleted records move to Trash for 30 days, then are permanently destroyed. Restoring from trash recreates the canonical_id and replays the external_ids map.