Usage & entitlements

Operations console: run live checks and commit/release reservations against the billing gateway, while analytics below pull aggregated usage and subscription signals from GET …/billing/admin/analytics/**. Charts refresh from the server — not the browser.

https://verify.verifystack.in/api/v1/billing

Usage & subscription analytics
See committed usage, plan-level rollups, and how subscriptions are spread across plans. Pick a date range, then refresh. Optional tenant filter applies when your gateway supports it.
Usage by feature
How much usage was committed per product feature in the selected period. Use this to see which checks or units drive load.
Technical reference — API path for integratorsGET /api/v1/billing/admin/analytics/usage-by-feature?from=&to=&tenantId=
No data for this range. Widen the dates, clear the tenant filter, or confirm billing is recording commits.
Usage by plan
Committed usage attributed to each plan. If you see “Unattributed,” the API did not send a plan code on those rows.
Technical reference — API path for integratorsGET /api/v1/billing/admin/analytics/usage-by-plan?from=&to=&tenantId=
No plan-level usage for this range. Your usage pipeline may need plan ids on each commit.
Subscriptions by plan
Active (or total) subscriptions per catalog plan — useful for capacity and revenue mix.
Technical reference — API path for integratorsGET /api/v1/billing/admin/analytics/subscriptions-by-plan
No subscription breakdown returned. Check that the billing admin analytics endpoint is enabled.
Recent entitlement activityCursor pagination
Checks, outcomes, and reservations from your gateway. Results are loaded in pages of 50 rows. Use Load next page until the server stops returning a cursor — that means you have reached the end. Columns follow the API payload.
Technical reference

Each response includes up to 50 events. Pass the returned cursor (or nextCursor) on the next request as ?cursor=… to fetch the following page.

GET /api/v1/billing/admin/analytics/entitlement-events?limit=50&cursor=

No events loaded yet. Use Refresh data above — the first page loads up to 50 events.

Check / reserve entitlement
POST /entitlements/check — featureCode must exist in the billing feature catalog (same list as GET …/admin/features).
Commit usage
POST /usage/commit — persists reserved units so they appear in committed usage analytics.
Release reservation
POST /usage/release — drops a hold without counting toward commits.

Uses the same reservationId field as commit.