Axle’s powerful API makes it easy for you to quickly retrieve detailed information from your users’ insurance policies. Here at Axle, we’re champions for consumer data control and privacy, so you’ll need to gain consent from the user to access their information.
POST
request to /ignition
. In return, you’ll retrieve an ignitionToken which
you’ll need to pass to your application’s client. This token will be used to initialize
Ignition and allows us to create secure, trackable session with your user. Ignition tokens do not expire.
authCode
) as an Ignition event via redirect parameters, Window MessageEvent, or webhook.
However, for additional security (particularly if the Ignition event is delivered to your application’s client), you’ll need to exchange the short-lived authCode
for a long-lived accessToken
in your application’s protected services.
authCode
expires after 10 minutes so be sure you’re exchanging codes in
real time.POST
request with your authCode
to token/exchange
. In
return you’ll receive an accessToken
, account
identifier, and list of policy
identifiers.
accessToken
, account
identifier, and list of policy
identifiers received in step 4 in your database - these values will be used to access account and policy information for the user going forward.
accessToken
that represents consent from the user and
can now leverage the Axle API to access their insurance data 🎉🎉!accessToken
, you can retrieve the Policy object that was shared by the user by making a GET
request to policies/{id}
with
the accessToken
passed in the x-access-token
header.