Analytics and Usage

The public API exposes tenant-scoped reporting for vendors that need traffic, latency, and request-usage visibility in their own systems.

Looking for per-resource breakdowns? This page covers org-wide totals.

• For per-link geo / device / browser / OS / referrer + time series, see URLs → Per-URL click analytics.
• For per-QR geo / device / scan method + time series, see QR Codes → Per-QR scan analytics.

Analytics overview

Use GET /api/v1/analytics/overview for organization-level URL metrics.

Typical uses:

• sync top-line link performance into an internal BI dashboard
• verify that API-created links are being attributed to the right tenant
• compare custom-domain activity across acme.com and example.io

Usage ledger

Use GET /api/v1/usage for API-operational visibility.

The response includes:

• recent request totals
• recent error totals
• average response time
• known API key activity
• recent request logs

This is the primary endpoint for customer-facing “developer portal” usage views.

Tenant guarantees

• usage data is filtered by bearer-token organizationId
• one tenant cannot read another tenant’s request logs or traffic summary
• request IDs, status codes, and response timing stay scoped to the calling organization