Sandbox

​

Accessing the sandbox

https://sandbox.axle.insure

https://ignition.sandbox.axle.insure

https://dashboard.sandbox.axle.insure

​

Testing Ignition completions in the sandbox

​

Result: link

​

Using test credentials to complete Login

1. Once an Ignition session has been generated (more details can be found here), select one of the test credentials based on which Axle scenario you would like to test. These credentials can be used for any carrier listed.
2. Input credentials into login page to simulate connecting to an insurance account for the selected carrier.
3. If applicable, complete the Ignition session by selecting a policy that you would like to test against.

Congrats! Now you can access sample Account or Policy objects after exchanging the generated authCode for an accessToken. See the Quickstart guide for more details.

​

Test credentials

Simple auto

The following credentials will connect to an account with several active auto policies.

username: username
password: password

Minimum auto

The following credentials will connect to an account with several auto policies, one of which has inactive status and one which satisfies only the minimum required policy coverage in most states.

username: user-auto-state-minimum
password: pass-auto-state-minimum

Simple home

The following credentials will connect to an account with several active home policies.

username: user-home
password: pass-home

Error

The following credentials will fail to connect to the Axle service, resulting in an errored status for the Ignition session.

username: user-error
password: pass-error

​

Result: manual

You can complete Ignition sessions manually by selecting “My carrier is not listed” on the carrier selection page and then uploading any document of the allowed types (defaults to pdf, jpg, jpeg, png).

​

Sending test documents through Axle’s Document AI

If your Axle client is configured to used Document AI, you can use the following test documents to complete Ignition sessions and receive the expected Policy response.

• Auto policy
• Home policy

​

Testing monitoring notifications in the sandbox

After completing an Ignition session and exchanging the authCode for an accessToken, you can trigger an Account event through POST /sandbox/account/{accountId}/event or Policy event through POST /sandbox/policies/{policyId}/event.

The following Account events and Policy events are supported:

account.modified

You can modify Account fields to simulate an account.modified event. The following example will change email, firstName, and phone fields on an existing Account.

{
  "email": "updatedEmail@axle.insure",
  "firstName": "Jane",
  "phone" "+14041230101"
}

account.disconnected

You can test account.disconnected event by setting the connection status to one of the “inactive” states. Refer to Account object for all the available cases.

{
  "connection": {
      "status": "credentials-expired"
  }
}

policy.modified

You can modify Policy fields to simulate a policy.modified event. The following example will set Policy as inactive (e.g., the policy has been cancelled) as well as update the Policy address.

{
  "isActive": false,
  "address": {
      "addressLine1": "New Street",
      "addressLine2": "New Apt",
      "city": "Atlanta",
      "postalCode": "30315",
      "state": "GA",
      "country: "USA"
  }
}