Webhooks & Alerts
Webhooks deliver push notifications when a monitored flight's status changes. Events use the same live flight status feed as Flight Status — your server receives HTTP POST callbacks instead of polling.
Requirements
x-api-key on every request (direct subscription). Learn more →Pro, Ultra, or Mega — BASIC cannot create webhooks
Learn more →| Plan | Max active webhooks |
|---|---|
| BASIC | 0 (create rejected) |
| PRO | 1 |
| ULTRA | 3 |
| MEGA | 10 |
Status is polled every 5 minutes. Subscriptions auto-disable after 10 consecutive delivery failures. Full plan detail: Rate Limits.
| Endpoint | Page | When to use |
|---|---|---|
POST /webhooks | Subscriptions | Register a callback URL for a flight |
GET /webhooks | Subscriptions | List subscriptions on your API key |
PATCH /webhooks/{webhook_id} | Subscriptions | Pause or resume without deleting |
DELETE /webhooks/{webhook_id} | Subscriptions | Permanently remove a subscription |
GET /webhooks/events | Event types | Discover supported event_types values |
| (inbound) | Callback Delivery | HTTP POST body your server receives |
Webhooks vs polling. For gate-change alerts, webhooks at 5-minute poll intervals are usually sufficient and far cheaper than sub-minute Flight Status polling. Use polling when you need on-demand lookups without a registered callback URL.
Error responses
Shared platform errors: Error Handling. Plan-gate:
403 — plan does not include webhooks
{
"detail": "Webhook subscriptions require PRO, ULTRA, or MEGA plan (current plan: BASIC)."
}Endpoint-specific errors (404 ownership, callback delivery) are on Subscriptions and Callback Delivery.
Related: Flight Status · Rate Limits