Start by identifying which surface is failing: portal, gateway, upstream, usage,
or billing.
Request is denied
Check the gateway response code. Then verify:
- product hostname is correct
- API key is present
- key is active
- subscription is active
- plan allows the requested usage
- credits are available if required
See Debug a denied request.
Request reaches gateway but not upstream
Likely causes:
- request was denied before forwarding
- upstream URL is wrong
- upstream authentication is missing
- route path does not exist upstream
Confirm whether the response is a gateway error or an upstream error.
Usage does not appear
Check:
- the request went through the gateway
- the request was allowed
- the expected meter is configured
- the usage consumer has processed events
- actual usage is returned by upstream if required
Subscriber cannot create a key
Check:
- subscriber is signed in to the correct portal
- subscriber has an active subscription
- product is published
- API key limits or policy are not preventing creation
Billing looks wrong
Check:
- meter names match plan configuration
- usage period is correct
- included usage and overage are configured as intended
- prepaid credit grants and spend are visible
- test traffic is not being confused with production traffic
Product docs are stale
Confirm:
- docs changes were committed to the correct product docs source
- webhook delivery succeeded
- managed docs bundle was published
- portal is reading the expected environment bundle