🛫
XClaim API Partner Docs
  • Introduction
  • Authentication
  • Claim Creation Workflows
    • Appendix
  • First Notice Of Loss (FNOL)
    • Get Claim Selector
    • Get Claim Types
    • Get Fnol
  • Claims
    • Create a new Claim
    • List of all claims
    • Update an existing Claim
    • Get Claim
    • Claim Policy Details
    • List of claims by booking reference
    • List of claims by claim type
    • Claim Files
      • Upload File
      • Upload File for an Existing Claim
      • List of Files by Claim
      • Get File
      • Delete File
  • Webhooks
    • Overview
    • Verifying signatures
    • Claim Webhooks
  • Integrations
    • Cancel For Any Reason (CFAR)
    • Claim Eligibility
      • Get Claim Eligibility Check
Powered by GitBook
On this page
  1. Webhooks

Overview

PreviousWebhooksNextVerifying signatures

Last updated 2 years ago

Webhooks are sent to every receiving url that is specified in the "webhooks" key on the claim creation request - you can check the "create a new claim" request in these docs for an example of how to do this. It is completely optional, so you can specify no webhook receivers, one or as many as you like (for example, if you have multiple separate parts of your ecosystem which you would like to receive these webhooks).

Inside the webhooks array of the aforementioned create claim request, you can specify receivers inside json objects. Each object should have a "url" and "key" property. The URL property specifies the URL that the webhook will be sent to, and the key is any string you choose, which is used to create a signature for each webhook sent (to the URL specified in the same webhook object), which will allow you to verify the authenticity of the sender (ie. XClaim).

For example, consider this:

    {
      "url": "http://some.site",
      "key": "abc123"
    }

Webhooks will be sent to ", and the signature created using the key "abc123".

http://some.site"