Support and operational investigation

Licenzy has a strict separation between runtime integration and operator workflows. Customer apps and backends use the public /v1 runtime endpoints. Human operators use the Licenzy portal for support, debug, configuration, and recovery.

• Use runtime /v1 endpoints from backend code for checkout, access checks, entitlement reads, and usage consumption.
• Use the portal for Stripe setup, products, API keys, support/debug operations, webhook inspection, and manual recovery.
• Runtime API keys cannot access admin, configuration, support, or operator workflows.

The Customer Support page in the Licenzy portal is organized around subject_ref. Operators can inspect the current runtime state for one customer or workspace without changing backend integrations.

• Inspect a customer by subject_ref.
• View the runtime access decision and any denial reason returned by Licenzy.
• Inspect current entitlements and effective availability.
• Review entitlement history for manual and lifecycle changes.
• Inspect checkout attempts for the same customer and mode.
• Inspect usage history for recent consumption events.
• Inspect outbound webhook deliveries, statuses, attempts, and HTTP results.

Manual actions live in the portal because they are operator workflows, not runtime API calls. Use them when support needs to recover customer access or correct entitlement state after review.

• Manual grant entitlement.
• Manual revoke entitlement.
• Manual adjust usage credits.

These actions are operational tools. They should be used deliberately after inspecting access, entitlement state, checkout history, and webhook delivery context.

For the exact operational flow around failed deliveries and portal-side requeues, pair this page with delivery debugging and retry flows. For the runtime effect of each manual action, use manual portal operations.

Runtime reads remain the correct integration surface when your application needs to make a backend decision or render customer state inside your product.

• POST /v1/access/check for the smallest allow or deny decision.
• GET /v1/customer/access/:subject_ref for a richer runtime customer access view.
• GET /v1/entitlements/:subject_ref for direct entitlement inspection in your app or backend.

Use those endpoints for app behavior. Use the portal when the task is investigation, audit, delivery tracing, or manual state recovery.