Alerts and support
Which developer alerts reach you by email or in the console, and the support tickets raised from the console.
3 routes
Alert topics are webhook_failures, budgets, production_decisions and secrets_expiring, each with email and in_app channels.
GET /v1/developer/alert-preferences
GET /v1/developer/alert-preferencesAuthentication- Developer console session
PUT /v1/developer/alert-preferences
PUT /v1/developer/alert-preferencesAuthentication- Developer console session
Body: { topics: [{ topic, channels: { email?: boolean, in_app?: boolean } }] }.
The body is checked by the service rather than by a declared class, so its fields are not listed here. The guide linked above describes what it takes.
GET /v1/developer/support/tickets
GET /v1/developer/support/ticketsAuthentication- Developer console session
What this does not do
- Responses are not listed. The API declares no response types, so this page describes what to send and who may send it. Recorded response shapes are on the guides.
- This page is generated. It was read from the API at commit
234dba22. Editing it by hand changes nothing; the next sync overwrites it.
Verified against API commit 234dba22 on 2026-10-18. The routes, scopes, checklist, events and limits on these pages are read from that export, not typed.