# Webhook event delivery FL3XX sends this request to the callbackUrl of your subscription when a subscribed event occurs. This is not an endpoint you call: it is the request your endpoint receives. Subscriptions are created with POST /api/v2/webhooks/subscriptions. The body is a notification only: it tells you which event happened and to which resource, but it does not contain the resource data. Use resourceId to retrieve the current state of the flight from the API. When several events occur for the same flight in a short period, they can be combined into one delivery. In that case subEventTypes lists every event type that was combined. See Grouped Deliveries in the Webhooks section for the event value a combined delivery carries. Verifying the signature Every request carries an X-Webhook-Signature header. It is the HMAC SHA256 of the raw request body, using the signingKey you set when creating the subscription as the secret, encoded as lowercase hexadecimal. Compute the same value over the body exactly as received, before parsing it, and reject the request if the values do not match. Do not rely on the order of the fields in the body. Responding Return a 2xx status code within 1 second. Any other status code, or no response in time, is recorded as a failed delivery and is not resent. Failed deliveries can be listed with GET /api/v2/webhooks/deliveries. After repeated consecutive failures, the subscription is set to INACTIVE and deliveries stop until its status is set back to ACTIVE with PATCH /api/v2/webhooks/subscriptions/{subscriptionId}. Endpoint: POST Your callback URL Version: 2.6.0 Security: ## Header parameters: - `X-Webhook-Signature` (string, required) Always sent by FL3XX. HMAC SHA256 of the raw request body, using the subscription signingKey as the secret, as lowercase hexadecimal. Example: "9b1f0c7e5d3a2b8c4e6f1a0d9c8b7a6e5f4d3c2b1a0f9e8d7c6b5a4f3e2d1c0b" - `X-Webhook-Event` (string, required) Always sent by FL3XX. The event type, same value as event in the body. Example: "FLIGHT_TIME_UPDATE" - `X-Webhook-Id` (string, required) Always sent by FL3XX. The event identifier, same value as eventId in the body. Example: "6735f1c2a9e4b7d1c0f3a8e2" - `X-Webhook-Timestamp` (integer, required) Always sent by FL3XX. Time the request was sent, in epoch milliseconds (UTC). Example: 1763291431512 ## Request fields (application/json): - `event` (string, required) Always sent by FL3XX. The event type. On a combined delivery this is either a group event type (FLIGHT_UPDATE, FLIGHT_PASSENGER_UPDATE) or the type of one of the combined events. Check subEventTypes for the full list. Example: "FLIGHT_TIME_UPDATE" - `eventId` (string, required) Always sent by FL3XX. Unique identifier of the event. Same value as the X-Webhook-Id header. Example: "6735f1c2a9e4b7d1c0f3a8e2" - `operatorId` (integer, required) Always sent by FL3XX. ID of the operator the event belongs to. Example: 1234 - `timestamp` (integer, required) Always sent by FL3XX. Time FL3XX recorded the event, in epoch milliseconds (UTC). Example: 1763291400000 - `resourceType` (string, required) Always sent by FL3XX. The type of the affected resource. Enum: "FLIGHT" - `resourceId` (string, required) Always sent by FL3XX. ID of the affected resource, sent as a string. For resourceType FLIGHT this is the FL3XX flight ID. Example: "4815162" - `mainEventId` (string) Only present on group events. Identifier of the event the group was built from. Example: "6735f1d8a9e4b7d1c0f3a8f4" - `subEventTypes` (array) Only present on group events. The event types combined in this delivery. Example: ["FLIGHT_TIME_UPDATE","FLIGHT_AIRCRAFT_UPDATE"] ## Response 200 fields