Skip to main content

Parametric Flight Protection

Flight Protection is a parametric travel product: instead of asking your customer to file a claim and wait for it to be assessed, Sitata monitors each covered flight and — when a qualifying disruption is detected — creates and pays out a claim automatically. There are no claim forms for the common cases, and the payout is a fixed, pre-agreed amount rather than a case-by-case assessment.

Covered disruptions include flight delay, cancellation, diversion, and missed connection, with optional baggage (delayed/lost) and airport lounge benefits. Which of these are enabled, the qualifying thresholds, the payout amounts, and any caps are all part of the product's configuration (see Integration).

info

Flight Protection is built on the same Products → Subscriptions machinery as the rest of Sitata's catalogue, so if you have already integrated Embedded Insurance the workflow will be familiar. The key difference is that after purchase you register the customer's flights so that Sitata can monitor them and trigger payouts. Contact us to have the Flight Protection products assigned to your organization.

The Annual Products

Flight Protection is sold as an annual product. Each tier covers a different number of trips per year (the trip allowance). Reference them by their universal_id:

Product (universal_id)Annual trip allowance
flight-protect-net-33 trips per year
flight-protect-net-66 trips per year
flight-protect-net-99 trips per year
flight-protect-net-1212 trips per year

When a customer registers a trip against their subscription, it consumes one of the trips in their annual allowance. Once the allowance is exhausted, further registrations are declined and a trip-limit event is emitted.

How It Works, End To End

  1. Sell the product. Quote and purchase a Flight Protection subscription for your customer — this is the annual "policy". See Integration.
  2. Register flights. Create a trip with the customer's flight segments and flag it for Flight Protection. Sitata binds the coverage and begins monitoring those flights.
  3. Sitata monitors and pays out. When a covered flight is disrupted beyond the configured threshold, Sitata automatically creates a claim, sets the payout amount, and collects the payout details from your customer.
  4. You receive events. Every step of the lifecycle is delivered to your servers as a webhook. If you operate as a whitelabel partner, the customer-facing messages are relayed to you so you can deliver them under your own brand.
  5. Your customer gets paid. Payouts are made once your customer provides their bank/payout details — either on Sitata's hosted claim page or through the Claims Widget embedded in your own portal. See Claims.

Authentication

All Flight Protection API calls use your organization's authentication token, exactly as described in the API reference. Send:

Authorization: TKN YOUR_COMPANY_TOKEN
Organization: YOUR_COMPANY_ID
warning

Never expose your organization's authentication token in a browser or mobile client. The embeddable Claims Widget uses a separate public token (Authorization: PUB ...) that is safe for front-end use and is restricted to your allow-listed referer domains.