Skip to main content
You can read more about our product releases on our blog!
​
September 29, 2025
Ignition
Deprecated:
  • The Axle team has deprecated passing in an access token to Start Ignition. No immediate changes are required if you use this feature, but it will no longer have the effect of disabling monitoring on the access token.
  • To disable monitoring for a given access token, check out our Descope Token API.
​
August 27, 2025
Ignition
Added:
  • You can now complete Ignition sessions on behalf of users, via Axle’s Proxy operations.
  • To learn more, check out our Proxy Ignition guide.
​
July 3, 2025
SandboxPolicy
Added:
  • You can now test Axle’s integrations with renters (HO-4) policies in the Axle Sandbox.
  • To learn more, check out our Testing Ignition guide.
​
June 20, 2025
Policy Validation
Added:
  • You can now access the third-party-match rule via Policy Validation.
  • To learn more, check out our Policy Validation guide.
​
June 18, 2025
Ignition
Changed:
  • When testing in the Axle Sandbox, the custom metadata object provided when generating a new Ignition session must NOT contain any nested keys. This is to ensure current visualization in the Axle Policy Report, easy search and filtering, and correct Validation Template processing.
// Supported
{ "key": "value" } 

// NOT supported
{ "key": { "key": "value" } }
  • You can view more details about the metadata field in the Start Ignition reference.
  • Before this change is reflected in the production environment, the Axle team will communicate via direct channels to all impacted clients.
​
June 13, 2025
Policy Validation
Added:
  • You can now access the vehicle-use-meets-requirements rule via Policy Validation.
  • To learn more, check out our Policy Validation guide.
​
May 6, 2025
Tokens
Changed:
  • When exchanging a token, 401 and 403 error states now include more detailed messaging on why an authCode cannot be exchanged for an accessToken.
  • You can view more details about these error states in the Exchange Token reference.
​
April 22, 2025
Policy Validation
Added:
  • You can now access the following rules via Policy Validation.
    • bodily-injury-coverage-meets-requirements
    • property-damage-coverage-meets-requirements
    • uninsured-underinsured-bi-coverage-meets-requirements
    • uninsured-underinsured-pd-coverage-meets-requirements
  • To learn more, check out our Policy Validation guide.
​
April 15, 2025
IgnitionSandbox
Added:
  • For supported carriers, you can now test Ignition completions through Axle Policy Lookup in the Axle Sandbox.
  • To learn more, check out our Testing Ignition guide.
​
April 10, 2025
Policy Validation
Added:
  • You can now access the properties-match rule via Policy Validation.
  • To learn more, check out our Policy Validation guide.
​
April 7, 2025
Policy
Added:
  • The Axle Policy object now includes the use of a type: vehicle property when available.
  • To learn more, check out our detailed Policy guide.
​
February 18, 2025
IgnitionSandbox
Changed:
  • When testing in the Axle Sandbox, it is now required to specify in user.id when generating a new Ignition session, as it is used for metrics & reporting, search, and an easier integration with less storage of data.
  • You can view more details about the user field in the Start Ignition reference.
  • Before this change is reflected in the production environment, the Axle team will communicate via direct channels to all impacted clients.
​
January 21, 2025
Policy Validation
Added:
  • You can now access the following rules via Policy Validation.
    • insureds-match
    • collision-coverage-meets-requirements
    • comprehensive-coverage-meets-requirements
  • To learn more, check out our Policy Validation guide.
​
December 20, 2024
Policy Validation
Added:
  • You can now access the expiration-date-comparison rule via Policy Validation.
  • To learn more, check out our Policy Validation guide.
​
October 2, 2024
IgnitionMonitoring
Added:
  • You can now specify a custom webhook header to be sent on all webhook events.
  • Please contact the Axle team if you would like to configure these for your Axle client.
​
October 9, 2023
Axle for Platforms
Added:
  • The Axle team is rolling out support for platform partners, who can now scalably offer Axle’s insurance verification services to their customers.
  • Platforms can manage their customers’ Axle integrations via the new destination clients feature. This includes the ability to create destination clients and call other Axle APIs on their behalf.
  • To learn more, check out the new Axle for Platforms guide.
​
May 24, 2023
Policy
Fixed:
  • Individual fields now support null type in Account and Policy response objects to improve data transparency and actionability
    • Individual fields will return null values when:
      • The carrier data source supports the field, but no information is present for the selected Account or Policy.
      • The carrier data source does not support that field.
    • Optional fields, such as Policy.coverages["BI"].property or Policy.coverages["UMPD"].deductible may return null or undefined
      • null - The carrier data source supports the field, but no information is present for the selected Account or Policy.
      • undefined - The carrier data source supports the field and data is available that specifies that the field does not exist on the Account or Policy. Example Policy:
{
	"...",
	"policyNumber": "123456789",
	"isActive": true,
	"effectiveDate": null,
	"expirationDate": "2023-10-22T04:00:00.000Z",
	"address": {
		"addressLine1": "123 Main St.",
		"addressLine2": null,
		"city": "New York",
		"state": "NY",
		"postalCode": "10014",
		"country": "US",
	},
	"coverages": [
		{
			"code": "PD",
			"label": "Property Damage",
			"limitPerAccident": null, // No information was available from carrier data source
			"deductible": undefined, // The carrier data source specifies that here is no deductible present for this coverage
			"property": "prp_83sD63h82bbeu2Dgn"
		},
		"..."
	],
	"..."
}
⌘I