Skip to main content

Claim Webhooks

Webhooks are how your systems learn that a claim has changed. Sitata sends a signed POST to your endpoint each time a claim is submitted, starts being evaluated, is accepted, denied, paid or reopened, needs bank details, or is withdrawn.

Who Receives Claim Events

For each claim event, Sitata sends a webhook to the enabled endpoints of:

  • the organization the claim's subscription (policy) belongs to, which is usually the partner that sold it;
  • every handler organization on the claim, meaning the owner of each product on the policy.

Each organization receives each event once, even if it has both roles. You don't need to own the product to receive these events. This makes webhooks the main way for a selling partner to follow claims. See Who Can See What.

Subscribe

Register a webhook endpoint and list the claim events you want in enabled_events:

curl -X POST "https://staging.sitata.com/api/v2/org/YOUR_COMPANY_ID/webhook_endpoints" \
-H "Authorization: TKN YOUR_COMPANY_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"webhook_endpoint": {
"enabled": true,
"url": "https://www.your-company.co/webhooks/sitata",
"enabled_events": [600, 601, 602, 603, 604, 605, 606, 607]
}
}'

If enabled_events is empty, the endpoint receives all events.

Claim Event Types

EventNameSent when
600Claim submittedThe traveller submits the claim, or resubmits it after editing (new → submitted).
601Claim evaluatingAn adjuster starts reviewing the claim (→ evaluating).
602Claim acceptedAn adjuster approves the claim (→ accepted).
603Claim deniedAn adjuster denies the claim (→ rejected).
604Claim paidAn adjuster manually marks an accepted claim as paid (→ payment_issued). See the note below.
605Claim reopenedAn adjuster reopens the claim (→ new).
606Claim bank info requestedAn adjuster asks the traveller for payout details (accepted → pending_bank_info).
607Claim withdrawnThe claim is withdrawn (→ withdrawn).
warning

Not every status change sends a claim event. Plan your integration around these cases:

  • Payments made through Wise don't send 604. Most claims are paid by sending a transfer to the bank details the traveller provided. When Sitata confirms that transfer, the claim moves to payment_issued, but no 604 is sent. (Automatic claims, such as Flight Protection, send 1010 at this point instead.) 604 is only sent when an adjuster marks a claim as paid by hand. If you handle the claim, you can read it to check whether its status has reached 5. If you only sell the policy, there is currently no event that tells you a Wise payment was made.
  • Claims that Sitata creates automatically don't send 600 or 606. They start in pending_bank_info and send 1009 instead. See Flight Protection notifications.
  • A traveller sending a claim back to draft (restart) doesn't send an event. The 600 sent when they resubmit is your signal.

Payload

Each delivery is a JSON webhook event. The claim details are in its payload:

{
"id": "5e2b9d8c-7a6f-4b3e-9d1c-2f0a8b7c6d5e",
"created_at": "2026-10-22T16:40:02.551203Z",
"updated_at": "2026-10-22T16:40:02.551203Z",
"company_id": "YOUR_COMPANY_ID",
"webhook_endpoint_id": "c1d2e3f4-a5b6-4c7d-8e9f-0a1b2c3d4e5f",
"attempt_count": 0,
"completed": false,
"next_attempt_at": null,
"last_response": null,
"last_response_status": null,
"payload": {
"event": 602,
"claim_id": "8b0d6a4e-2f63-4a51-9a0e-3c9f2d7b1e55",
"claim_human_id": "4F9A2C",
"status": 3,
"subscription_id": "0c7f1a8e-6d0b-4c1e-9a52-7b7f3f1c2d10",
"user_id": "f118f42a-3b9e-479d-94c3-9ee18fa36e4a",
"air_segment_id": null,
"trip_id": null,
"trigger_event": null,
"category_key": "medical",
"currency_code": "USD",
"value_requested": 125000,
"value_accepted": 98000,
"outcome_desc": "Approved less the policy excess.",
"adjuster_name": "Jane Adjuster"
}
}

Payload fields: events 600–605 and 607

AttributeTypeDescription
eventIntegerThe event type (600–605, 607).
claim_idStringThe claim's UUID. Read the claim with it if you handle the claim.
claim_human_idStringThe claim's short reference.
statusIntegerThe claim's status after the change. See The Claim Lifecycle.
subscription_idStringThe policy the claim is made against. Use it to match the claim to your own policy record.
user_idStringThe claimant's Sitata user id.
air_segment_id / trip_idStringOnly for automatic flight claims. Otherwise null.
trigger_eventStringOnly for automatic claims. Otherwise null.
category_keyStringThe claim category, once known.
currency_codeStringThe claim currency.
value_requestedIntegerThe amount requested, in the currency's smallest unit.
value_acceptedIntegerThe amount approved, in the currency's smallest unit. It is 0 when denied and null before a decision.

Some events add more fields:

EventExtra fields
602 accepted, 603 deniedoutcome_desc (the adjuster's explanation, which for a denial is the reason) and adjuster_name.
604 paidpayment_ref and payment_at.

Payload fields: event 606

The bank-info-requested payload is smaller. It has event, claim_id, claim_human_id, air_segment_id, trip_id, trigger_event, category_key, currency_code and value_accepted. It does not have status, subscription_id, user_id or value_requested. Use claim_id to match it to the claim's earlier events.

info

Webhook payloads hold identifiers and amounts, not the full claim object, its answers or its documents. If you handle the claim, call the organization claims API for the details.

Verify, Acknowledge And Retry

Claim events are signed and retried the same way as every other Sitata webhook:

  • Each delivery has a Sitata-Signature: t=<timestamp>,v1=<signature> header. The signature is an HMAC-SHA256 of "<t>.<raw request body>", keyed with your endpoint's signing_secret and hex-encoded in uppercase. Compare it without regard to case. For a step-by-step guide, see Verify the signature.
  • Respond with any 2xx status to acknowledge the event. Sitata retries any other response, or a connection failure, with exponential backoff.
  • If an event arrives twice, the top-level id is the same, so you can use it to deduplicate. Events can arrive out of order, so treat the status in the payload, or a fresh read of the claim, as the truth rather than the order of arrival.

Testing

On staging, the developer-notification tool (POST /dev_notifications) sends a fake version of each claim event (600–607) to your endpoint. Nothing is written to the database. It is described under Testing With The Simulation Endpoints. The fake claims use made-up ids, so use them to test parsing and signature checks, not to look up claims.

To test the whole flow on staging, file a claim as a test traveller (through the Claims Widget or the traveller API), submit it, and watch for 600. Then ask your Sitata contact to move the claim through evaluation and a decision so you receive 601 and then 602 or 603.