Skip to main content
Most integration problems fall into a handful of shapes, and each has a fast check. Find your symptom below, run the check, and follow the link for the full write-up.

What symptom are you seeing?

The auth check, with your key in $KEY:
A 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

Or send any request with --debug. A 401 here ends the investigation: the key is wrong for this region or environment.
2

Confirm the object exists where you think

Exit code 4 means the customer is not in this environment.
3

Send one event and watch it

Open the Event Debugger and find it. If it is there but unmatched, the event name or customer is wrong. If it is matched but the number is off, the aggregation property is wrong.
4

Check the invoice preview

This shows what the next invoice would charge right now. A missing line item means the feature is not priced in the plan.

Deeper troubleshooting guides

Still stuck?

Bring the request ID or the svix-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.