> ## Documentation Index > Fetch the complete documentation index at: https://docs.axle.insure/llms.txt > Use this file to discover all available pages before exploring further. # Testing Ignition > The Axle sandbox can be used to test your integration of Axle's API in your application or platform. All Axle API endpoints can access the sandbox environment. If you have not received access to the Axle sandbox, please reach out to the Axle team! ## Accessing the sandbox #### API Sandbox Url ```bash theme={null} https://sandbox.axle.insure ``` #### Ignition Sandbox Url ```bash theme={null} https://ignition.sandbox.axle.insure ``` #### Dashboard Sandbox Url ```bash theme={null} https://dashboard.sandbox.axle.insure ``` ## Testing Ignition completions in the sandbox ### Result: `link` #### Using test credentials to complete Login 1. Generate an `Ignition` session. ([more details can be found here](/api-reference/ignition/start-ignition)) 2. Once an `Ignition` session has been generated , 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. 3. Input credentials into login page to simulate connecting to an insurance account for the selected carrier. 4. If applicable, complete the Ignition session by selecting a policy that you would like to test against. Congrats! Now you can access sample [Account](/api-reference/accounts/account) or [Policy](/api-reference/policies/policy) objects after exchanging the generated `authCode` for an `accessToken`. See the [Quickstart](/guides/quickstart) guide for more details. #### Test user credentials The following credentials will connect to an account with a comprehensive set of `auto` policies. ``` username: user-auto password: pass-auto ``` Policies: * `2019 Mercedes-Benz C 300` — Active **current term** auto policy for a 2019 Mercedes-Benz C 300 * Renewal term is available and will be immediately available via Axle API when this policy is selected. In Get Policy API call, provide optional `term=renewal` query parameter. More info can be found [here](/api-reference/policies/get-policy#parameter-renewal). * `2013 Hyundai Sonata` — Active **current term** auto policy for a 2013 Hyundai Sonata * Renewal term is available and will be immediately available via API when this policy is selected. * `Missing expiration date` — Policy with expiration date null * `Missing documents` — Policy with no documents * `Missing several policy details and no documents` — Policy missing coverages, expiration date, insureds, and premium and has no documents * `State Minimum` — Active auto policy which represents the minimum state-required coverage in most states (only BI and PD coverage) The following credentials will connect to an account with several active `home` policies. ``` username: user-home password: pass-home ``` Policies: * `123 Fake St., Atlanta, GA 30303` — Active **current term** home policy for this address * Renewal term is available and will be immediately available via Axle API when this policy is selected. In Get Policy API call, provide optional `term=renewal` query parameter. More info can be found [here](/api-reference/policies/get-policy#parameter-renewal). * `123 Sample Ln., Atlanta, GA 30303` — Active **current term** home policy for this address * Renewal term is available and will be immediately available via API when this policy is selected. * `Missing policy details` — Policy missing key details, including effective and expiration dates, premium, and third parties * `Missing policy details and documents` — Policy missing details, including effective and expiration dates, premium, and third parties, and has no documents * `Pre-effective policy` — Pre-effective policy, an active policy with an effective date in the future * `Missing policy details and documents` — Policy missing details, including effective and expiration dates, premium, insureds, and third parties, and has no documents * `Missing policy details` — Policy missing key details, including effective and expiration dates, premium, insureds, and third parties. * `Missing declaration page` — Policy with documents but only includes a policy agreement, not a declarations page. * `Missing insured types` — Policy missing insured types. The following credentials will connect to an account with an active `renters` policy. ``` username: user-renters password: pass-renters ``` Policies: * `123 Main St, Unit 456, Atlanta, GA 30303` — Active renters policy for this address. The following credentials will connect to an account with several active `flood` policies. ``` username: user-flood password: pass-flood ``` Policies: * `123 Fake St., Atlanta, GA 30303` — Active flood policy for this address. * `Missing documents` — Flood policy with no documents. * `Missing coverage details` — Flood policy missing coverage details * `Missing policy details and no documents` — Policy missing multiple details and has no documents. 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 ``` Policies: * This credential simulates an error during the account step so no policies are available. #### Using test inputs to complete Policy Lookup 1. After generating an `Ignition` session, select one of the below test inputs based on which Axle scenario you would like to test. These inputs can only be used for carriers that support Policy Lookup. 2. Navigate to a carrier which supports Policy Lookup. 3. Click on "Search your policy number" to arrive at the Policy Lookup page. 4. Type in the test inputs and click on "Search" to simulate searching for policy details from the selected carrier. After seeing the Success page, you can now access sample [Account](/api-reference/accounts/account) or [Policy](/api-reference/policies/policy) objects after exchanging the generated `authCode` for an `accessToken`. See the [Quickstart](/guides/quickstart) guide for more details. #### Test credentials for Policy Lookup **Active Policy** The following test inputs will connect to a sample `auto` policy. ``` Policy number: A123456789 VIN: 12345 ``` **Inactive Policy** The following test inputs will connect to a sample inactive `auto` policy. ``` Policy number: A12121212 VIN: 12121 ``` **Active Policy** The following test inputs will connect to a sample `home` policy. ``` Policy number: H123456789 Postal code: 30303 Address (for Ignition Proxy only): Enter either any valid US address string or an address object with `addressLine1`, `addressLine2`, `city`, `state`, `postalCode`, and `country` insuredName (for Ignition Proxy only): "John Smith" ``` **Inactive Policy** The following test inputs will connect to a sample inactive `home` policy. ``` Policy number: H121212121 Postal code: 30303 Address (for Ignition Proxy only): Enter either any valid US address string or an address object with `addressLine1`, `addressLine2`, `city`, `state`, `postalCode`, and `country` insuredName (for Ignition Proxy only): "John Smith" ``` The following inputs will fail to connect to the Axle service, resulting in an `errored` status for the Ignition session. ``` Policy number: 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`). Your Axle `client` will be configured in the sandbox to mirror what will be used by your application's production environment. Contact the Axle team if you would like to make any changes, such as enabling "manual" Ignition completions. #### 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. #### Document AI failure and inaccuracy cases If your Axle `client` is configured to use Document AI, you can use the following test documents to simulate failure and inaccuracy scenarios. Do not change the name of the documents and upload them through the Ignition flow to trigger the corresponding behavior. Use the following test documents for auto policies. These documents will return a successful response with missing or incomplete data fields in the resulting Policy. These documents will trigger Document AI errors. Upload a file named `enhanced-manual-push-through` (any extension) to simulate Document AI failing to extract data and the case where we are unable to process the document. After multiple attempts, Axle will automatically fall back to the enhanced manual push-through flow, accepting the original source file as uploaded, and the policy will be created with carrier set to "Other" and minimal data fields. Use the following test documents for home policies. These documents will return a successful response with missing or incomplete data fields in the resulting Policy. These documents will trigger Document AI errors. Upload a file named `enhanced-manual-push-through` (any extension) to simulate Document AI failing to extract data and the case where we are unable to process the document. After multiple attempts, Axle will automatically fall back to the enhanced manual push-through flow, accepting the original source file as uploaded, and the policy will be created with carrier set to "Other" and minimal data fields.