What symptom are you seeing?
The auth check, with your key in
$KEY:
200 with an items array means the key and region match. Swap in https://api.cloud.flexprice.io/v1 if you get 401.
Tools that show what happened
Event Debugger
Every ingested event with how it matched a feature and aggregated. The first stop for any metering question.
Webhook logs
Each delivery attempt, the response your endpoint returned, and a replay button.
CLI with --debug
Dumps the exact request and response with secrets redacted. Fastest way to see what the API actually received.
Ingestion monitoring
Throughput and rejection counts over time, to tell a code bug from a traffic change.
Run a five-minute diagnostic
1
Confirm the key and region
--debug. A 401 here ends the investigation: the key is wrong for this region or environment.2
Confirm the object exists where you think
4 means the customer is not in this environment.3
Send one event and watch it
4
Check the invoice preview
Deeper troubleshooting guides
- Usage events troubleshooting: the long version of every metering problem
- Validating events: what the ingest endpoint checks and what it does not
- Error responses: every status code and the error body shape
- API key troubleshooting: keys that stopped working, lost keys, and role errors
- MCP server troubleshooting: connection, URL, and Docker problems
- Self-hosting troubleshooting: containers, migrations, and Kafka
Still stuck?
Bring the request ID or thesvix-id, the environment, the region, and the exact time to support@flexprice.io or the community Slack. Check the status page first if every request is failing at once.
