Skip to main content
Policy updates are not enabled by default. Reach out to your Axle contact to enable them for your client.
Policy updates let you request carrier-side changes to a policy on behalf of your user. Once submitted, Axle processes the request and the policy changes once the update is complete.

How it works

  1. Your user connects their policy through an Ignition session.
  2. You request a policy update on that policy with an operation, the change to make.
  3. Axle checks that the policy’s insurance carrier and policy type support the operation, then sends the request to the insurance carrier.
  4. Axle sends policy update events to your webhookUri as the update moves through its lifecycle.

Operations

Which insurance carriers and policy types support an operation, which input fields it accepts, and whether it processes instantly depend on the operation. For a policy whose insurance carrier or policy type an operation doesn’t support, Request Policy Update returns 400 with policy-update-not-supported.

processesInstantly

Every policy update returns a processesInstantly flag. It tells you whether the insurance carrier applies the change as soon as it accepts the request:
  • processesInstantly: true - If the policy update succeeds, the change is reflected on the policy right away. Axle then retrieves the updated policy and sends policy-update.policy-refresh-succeeded or policy-update.policy-refresh-failed right after policy-update.request-succeeded.
  • processesInstantly: false - The insurance carrier applies the change later, even if the request itself was successful, so you’ll only receive events up through policy-update.request-succeeded or policy-update.request-failed. To find out when the policy has been updated, opt in to Monitoring to receive the policy.modified event.
The flag depends on the operation and the insurance carrier. Each operation’s page lists it.