Use this recipe after product configuration is done and before inviting external
subscribers.
Run a full subscriber test
- Open the production portal.
- Subscribe as a test customer.
- Create an API key.
- Call the production product hostname.
- Confirm the upstream response.
- Confirm usage arrives in core.
- Confirm billing behavior matches the plan.
Test failure paths
Validate:
- missing API key
- invalid API key
- revoked API key
- inactive subscription
- usage over limit
- insufficient credits if applicable
Confirm docs
Product docs should include:
- authentication example
- first successful request
- plan limits
- billing units
- common errors
- support path
Confirm operations
Before launch, know:
- who owns the upstream API
- who can change product config
- who can revoke keys
- where denied requests are inspected
- where usage is inspected
- how product docs are updated
Launch day
Start with a small subscriber group. Watch:
- successful gateway traffic
- denied request codes
- upstream errors
- usage event flow
- billing totals
- gateway latency
After the first traffic window looks healthy, expand access.