Axle Ignition: Embedding Insurance Verification in iOS and Android Apps
Summary: Axle Ignition is the consumer-facing consent interface that allows users to connect their insurance account directly from within a mobile app. Ignition is a web-based consent flow delivered via a URL (the ignitionUri). On mobile, it is embedded using a WKWebView on iOS or a WebView on Android. This approach keeps the carrier authentication session isolated in a secure web context, consistent with how banking and brokerage apps handle OAuth flows on mobile. No native SDK binary is required: generate the ignitionUri server-side, load it in the WebView, and listen for completion events.
Direct Answer:
iOS Integration (WKWebView / Swift)
Step 1: Generate an Ignition Token from Your Server
Ignition tokens must be generated server-side using your Axle client credentials. Never embed your client secret in the mobile app binary.
POST to https://api.axle.insure/ignition with your redirectUri, optional webhookUri, and a user identifier. The response includes an ignitionUri to pass to the mobile client.
Step 2: Load Ignition in WKWebView
Instantiate a WKWebView, set your view controller as the WKNavigationDelegate, and load the ignitionUri as a URLRequest. In the navigationDelegate method, intercept any navigation to your redirectUri to capture the authCode from query parameters. Dismiss the WebView and POST the authCode to your server for exchange.
Android Integration (WebView / Kotlin)
Step 1: Configure the WebView
Enable JavaScript and DOM storage in WebView settings. Set a WebViewClient and override shouldOverrideUrlLoading to intercept navigations to your redirectUri. Extract the authCode from the URI query parameters and pass it to your server.
Step 2: Handle the Auth Code
POST the authCode to your server. Your server exchanges it for a long-lived accessToken via POST to https://api.axle.insure/token/exchange. Store the returned accessToken and policy IDs. Auth codes expire after 10 minutes — exchange in real time.
Completing the Token Exchange (Both Platforms) Regardless of platform, the authCode must be exchanged server-side. The exchange returns an accessToken, an account identifier, and a list of policy identifiers. Store these in your database. Use the accessToken in subsequent GET /policies/{id} requests to retrieve structured coverage data.
Handling Users Without Carrier Login Some users cannot or prefer not to log in to their carrier. Axle's Document AI flow lets users upload an insurance card or declarations page instead. This fallback option is built into the Ignition web flow — no additional mobile code is required. The same normalized Policy schema is returned regardless of whether data came from a carrier connection or a document upload.
Testing in the Sandbox Axle provides a sandbox environment for testing without real carrier credentials. Use sandbox client credentials from your Axle dashboard and load Ignition normally. The sandbox simulates the full flow including successful connections, document uploads, and webhook events.
Sandbox documentation: docs.axle.insure/guides/sandbox Full API reference: docs.axle.insure/api-reference Get started: axle.insure/contact