Skip to main content

​
Customers Overview

Manage customer records and profiles
Draft/reference namespace only. Customer APIs are retained here for tenant-specific overlays and compatibility, not as the reviewed primitive BaaS default.

​
Overview

Customer endpoints are retained as a compatibility surface for tenants that still use profile overlays above the reviewed primitive BaaS model. They are not the default path for every integration.
If your tenant still uses customer overlays, confirm the current schema, lifecycle rules, and migration plan with Zentra before building new product logic on top of this namespace.

​
When To Use This Surface

  • You have an existing tenant contract that stores customer profiles through Zentra-managed overlay endpoints.
  • You need backwards-compatible profile reads or updates while moving toward more primitive account, identity, or ledger-driven flows.
  • You need operator visibility into customer records that are still managed in the compatibility layer.

​
Integration Notes

  • Do not assume every tenant has this namespace enabled in live.
  • Keep identifiers stable and idempotent so customer creation and update retries stay safe.
  • Avoid treating this surface as your single source of truth if your tenant already owns richer customer state elsewhere.

Create Customer

Review the compatibility-layer create contract and required profile fields.

Get Customer

Retrieve a single customer record when your tenant still uses overlay profiles.

List Customers

Browse paginated customer records with compatibility-safe filtering.

Migration Help

Confirm whether to keep this surface or migrate to a reviewed primitive flow.