ZB Customer 360 API Documentation
ZB Customer 360 recognises one customer across every ZB channel. Producers post an append-only stream of events, the service resolves each event's identity into a single graph keyed on the ZB ID subject, and consumers read a unified profile, a global event feed, loyalty membership, and per-product insights from one API.
Getting started
Every integration talks to one base URL, https://c360-api.lioncapventures.com, and every route lives under /v1/. A Customer 360 admin mints your service a key prefixed c360_ with the scopes you need, you store it in your own project's Secret Manager, and you send an X-API-Key header on every request. There is no user session and no OAuth handshake: authentication is a single header per calling service.
What the API does
Customer 360 is the data-unification layer for the ZB platform. Instead of every app guessing whether two records are the same person, they all emit events to one service that maintains the identity graph:
- One append-only event stream. Producers
POST /v1/eventsin batches of up to 500. Ingest is idempotent on(source, eventId), so a retry or a repair pass is always a safe no-op. - One unified customer. The resolver folds a customer's per-platform identities into a single graph keyed on the ZB ID subject UUID. A registered user can absorb a prior guest through an explicit
identity.claimedevent. - One profile to read. Consumers read a customer's identities, consents, and computed traits with the
profilescope, following the merge chain to the surviving customer. - One loyalty spine. The service is the dedup authority for a customer's SmileRewards
memberId: one member per customer, one customer per member. - One insights surface. Per-product aggregates over billers, loans, merchants, events, and mall products, all on the fee-free money basis the producers stored.
This service computes no money
Money fields cross the API as decimal strings and are validated only as Decimal >= 0, then stored verbatim. Customer 360 never derives a fee, tax, commission, discount, or total; the read-time trait engine only sums what you stored. See Events for the money convention.
Guides
Authentication & scopes
Learn how the X-API-Key header, sha256 storage, and the scope model work.
Resources
Event feed & parity
Read the append-only feed with an afterId cursor, key on eventId, and reconcile gaps with counts and exists.
Identity resolution
How the ZB ID subject auto-merges, why phone and email never auto-merge, and reading a unified profile.
Loyalty
Resolve a customer to a SmileRewards member id, the dedup authority, with created, exists, and conflict outcomes.
Insights
Per-product aggregates across billers, loans, merchants, events, and mall products on a fee-free money basis.
Errors
The success envelope, stable machine error codes, per-event ingest results, and validation error shapes.