Skip to main content
Once an insurance policy is connected through an Ignition session, Axle can monitor that policy for updates. These updates will trigger events that are sent from Axle to your systems via webhook or to your organization via communication channels such as email.
Policy events are only sent for insurance policies connected through Axle Ignition sessions that are configured with monitoring enabled. Please contact the Axle team if you would like to enable this feature.

​
Webhooks

You must specify a webhookUri when generating an Ignition token to receive webhook events. See Start Ignition for more details.Custom webhook headers can be configured to support uses cases like authentication. Please contact the Axle team if you would like to configure custom webhook headers.
A POST request will be sent to the webhookUri with the following payload. All events will include client, account, ref (Policy object identifier), user (optionally specified when generating Ignition token), and metadata (optionally specified when generating Ignition token). The exception is policy.renewal-available, which has its own payload.
Example webhook payload

​
policy.modified

This event type indicates details on the Policy changed. Refer to Policy for more details on the fields that can be modified.
Axle performs safety checks on policy modifications before sending a policy.modified event. This may cause a short delay between when policy information was refreshed from the carrier and when you receive notification of the event.

​
policy.renewal-available

This event type indicates renewal policy is available for retrieval. Refer to Policy for more details on available options and how to retrieve it. Unlike other Policy events, this payload identifies the Policy with policy instead of ref, doesn’t include client, and includes the renewal term’s effectiveDate and expirationDate.
Example webhook payload
If the Get Policy API endpoint returns a 404, it means no renewal policy is available. We recommend calling the API again without the term query parameter OR passing in term=current as a query parameter.

​
policy.result-detail-changed

This event type indicates Axle changed how it retrieves the policy, so the Policy’s resultDetail changed. For example, if a user portal login stops working, Axle can keep monitoring the policy through a policy lookup instead of disconnecting it. The event includes the new resultDetail and the previousResultDetail.
Example webhook payload
A new source can return different policy details, for example a policy lookup often returns less than a user portal login. The event doesn’t list which fields changed, so we recommend calling Get Policy to refresh your copy of the policy.

​
Special Policy Changes

If a policy.modified event indicates that a policy’s isActive field has changed to null, then the policy may have been removed from the account. It is recommended to reach out to the user to re-connect the policy for the existing account or link a new account.