After a policy is purchased via the Battleface Partner API (POST /policies), register the policy for flight monitoring by submitting the insured flight details — carrier, flight number, date, and passenger details — to the policy flight registration endpoint.
Set up a webhook endpoint in your infrastructure to receive Battleface claim event callbacks; register your webhook URL in the Battleface partner portal and note the shared secret for signature verification.
On receipt of a claim_triggered event (sent when the monitored flight delay exceeds the policy threshold), validate the webhook signature using the shared secret; parse the payload for policy_id, claim_id, delay_minutes, and payout_amount.
Update your booking record to reflect the triggered claim and payout status; notify the passenger that a claim has been filed on their behalf and provide the claim_id for reference.
For policies requiring customer evidence submission (non-parametric products), construct the claim evidence package — boarding pass, delay certificate, booking confirmation — and submit via POST /claims/{claimId}/evidence.
Track claim resolution via GET /claims/{claimId}; on status change to paid, confirm the payout method (bank transfer or card refund) and close the claim in your records.
Known gotchas
Battleface's flight monitoring is based on their flight data feed, not your booking system's status — discrepancies between your delay detection and Battleface's trigger can cause customer confusion; treat the Battleface determination as authoritative for the insurance claim.
Webhook delivery can be retried by Battleface on failure — implement idempotent processing keyed on the claim_id to avoid filing duplicate notifications or customer alerts.
Battleface policies are jurisdiction-constrained; the eligible countries and products differ by partner agreement — validate product availability at quote time and gracefully handle 422 responses for unsupported passenger nationalities.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp