# Support & status

Where to look when something breaks.

## Self-service first

| Symptom | Look here |
| --- | --- |
| Calls rejected | Logs → status codes, then [rate limits](/docs/dev/app-api/rate-limits) |
| Events missing | Sandbox → webhook deliveries and subscriptions |
| Install fails | Redirect URI exact match, PKCE verifier, mode of the client id |
| Payout not arriving | Payout account status and the threshold |

## Platform status

Live and historical incidents are on the status page linked from the developer dashboard. Subscribe there to be paged before your merchants notice.

## Contacting us

Open a ticket from **Support** in the developer dashboard. Include the **app number**, the mode, the installation id and a request id from the logs — with those three we usually answer in one round trip.

Target first response: one business day; review questions are answered inside the review thread.

## Deprecations

Breaking changes are announced at least **90 days** ahead by email and in the changelog, with a migration note. Additive changes — new fields, new event types — ship without notice, so build tolerant parsers.