Skip to main content

​
Tenant Analytics

The analytics namespace is retained in Mintlify as a compatibility and tenant-overlay reference, not as part of the reviewed public BaaS gateway contract.
Analytics routes are intentionally excluded from docs/current/api-specs/reviewed-public-route-manifest.yaml. Do not assume older tenant analytics endpoints are available in every environment.

​
Current Status

  • analytics is a tenant-specific or internal-style overlay surface
  • route shapes, auth model, and export capabilities can differ by tenant
  • older docs examples may refer to /tenants/{tenantId}/analytics style routes, but those are not reviewed public primitives

​
What This Surface Usually Covers

  • dashboard summary metrics
  • time-series metric queries
  • custom metric ingestion
  • analytics export jobs
  • tenant-specific alerting or reporting hooks

​
How To Use This Page

Use this page to understand the capability category, not to infer a stable public HTTP contract. If your tenant has analytics enabled:
  • request the tenant-issued analytics contract from Zentra
  • verify the exact route set, auth model, and retention behavior for your environment
  • keep analytics integrations out of your core money-moving control path
  • use the reviewed API surfaces under transfers, virtual accounts, cards, identity, and webhooks for core operational flows
  • use the console for operator-facing summaries when you do not need a tenant-specific analytics API

​
Next Steps

Analytics Overview

See the capability-level analytics summary

Console

Use the operational console for reviewed internal reporting workflows

Support

Request the tenant-issued analytics contract