[{"data":1,"prerenderedAt":129},["ShallowReactive",2],{"search-api":3},[4,11,20,30,38,48,56,64,72,83,92,102,111,117],{"id":5,"path":6,"dir":7,"title":8,"description":7,"keywords":9,"body":10},"content:0.index.md","\u002F","","Home",[]," Axitech Widget Axitech Widget is a versatile and robust tool designed to empower clients with a seamless integration of insurance claim experiences within their own web applications. What's included Seamless Integration We ensure a consistent and streamlined user experience, enhancing customer satisfaction Customizable With a wide array of configuration properties, the widget can be tailored to match your application's branding and requirements Comprehensive Claim Types The widget covers a variety of claim types, including accidents, thefts, damages, and more",{"id":12,"path":13,"dir":7,"title":14,"description":15,"keywords":16,"body":19},"content:1.guide:index.md","\u002Fguide","Getting Started","The Axitech Widget makes it easy to integrate insurance claim experiences into your own web applications. This repository provides two methods of using the widget; installation via npm, and usage through a CDN URL.",[17,18],"Installation","Standalone mode"," Getting Started The Axitech Widget makes it easy to integrate insurance claim experiences into your own web applications. This repository provides two methods of using the widget; installation via npm, and usage through a CDN URL. Installation The process of integrating the Axitech Widget into your application is straightforward: Choose the installation method that suits your project: npm installation or CDN usage. For detailed instructions, refer to the Installation section. Using npm: \nTo install the Axitech Widget from npm, run the following command in your project directory: npm install axitech-widget --save\n Using CDN: \nAlternatively, you can include the widget in your HTML file using a CDN URL: \u003C script src = \"https:\u002F\u002Funpkg.com\u002Faxitech-widget@1.0.0\u002Fdist\u002Faxitech-widget.umd.js\" >\u003C\u002F script >\n Follow the installation steps provided above for your chosen method. Utilize the sample code under the \"Usage\" section to initialize the widget in your application, customizing the configuration properties according to your requirements. Monitor the onSuccess and onError callbacks to handle successful claim submissions and potential errors. By following these steps, you can swiftly integrate the Axitech Widget and elevate the insurance claim experience for your users. Standalone mode The Axitech Widget also offers a standalone mode, allowing you to integrate the widget without npm installation. In standalone mode, you need to make an API request to our API, which will generate access URLs for each of your users. Additionally, you can request submissions for each user by making another API request. Include the user's ID in the request to retrieve relevant information. html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"id":21,"path":22,"dir":23,"title":17,"description":24,"keywords":25,"body":29},"content:1.guide:install.md","\u002Fguide\u002Finstall","guide","To seamlessly integrate the Axitech Widget into your web application, you have two options: using npm for a controlled package installation or utilizing the CDN for quick access.",[26,27,28],"Using npm (Node Package Manager)","Using CDN (Content Delivery Network)","Usage"," Installation To seamlessly integrate the Axitech Widget into your web application, you have two options: using npm for a controlled package installation or utilizing the CDN for quick access. Using npm (Node Package Manager) npm install axitech-widget --save\n Using CDN (Content Delivery Network) For rapid inclusion, you can integrate the widget via CDN. Simply add the following script tag to your HTML file: \u003C script src = \"https:\u002F\u002Funpkg.com\u002Faxitech-widget@1.0.0\u002Fdist\u002Faxitech-widget.umd.js\" >\u003C\u002F script >\n Usage Utilizing the Axitech Widget within your application is an intuitive process. Refer to the detailed usage for comprehensive examples on initializing the widget, customizing its behavior, and handling events. For a quick glance, here's two sample usage scenario: ES Module If you've installed the widget using npm and are using it as an ES module, you can import and use it in your JavaScript code like this: import { load } from 'axitech-widget' ;\n \n load ( 'YOUR_API_KEY' , {\n type: 'claim' ,\n clientId: 'YOUR_CLIENT_ID' ,\n policy: {\n provider: 'ABC Insurance' ,\n number: 'P12345' ,\n validTo: '2001-01-01' ,\n validFrom: '2000-01-01' ,\n vehicle: {\n licensePlate: 'XYZ-123' ,\n },\n holder: {\n phone: '987-654-3210' ,\n email: 'user@example.com' ,\n firstName: 'John' ,\n lastName: 'Doe' ,\n },\n linkedContacts: [\n {\n firstName: 'Jane' ,\n lastName: 'Doe' ,\n email: 'jane.doe@test.com' ,\n },\n {\n firstName: 'Test' ,\n lastName: 'User' ,\n email: 'test@test.com' ,\n },\n ],\n },\n onSuccess: console.log,\n onError: console.log,\n });\n UMD (Global) Version If you're using the UMD version via the CDN, you can load and initialize the widget within a DOMContentLoaded event listener: \u003C script >\n window. addEventListener ( 'DOMContentLoaded' , ( event ) => {\n ClaimsWidget. load ( 'YOUR_API_KEY' , {\n clientId: 'YOUR_CLIENT_ID' ,\n policy: {\n provider: 'ABC Insurance' ,\n number: 'P12345' ,\n validTo: '2001-01-01' ,\n validFrom: '2000-01-01' ,\n vehicle: {\n licensePlate: 'XYZ-123' ,\n },\n holder: {\n phone: '987-654-3210' ,\n email: 'user@example.com' ,\n firstName: 'John' ,\n lastName: 'Doe' ,\n },\n linkedContacts: [\n {\n firstName: 'Jane' ,\n lastName: 'Doe' ,\n email: 'jane.doe@test.com' ,\n },\n {\n firstName: 'Test' ,\n lastName: 'User' ,\n email: 'test@test.com' ,\n },\n ],\n },\n onSuccess: console.log,\n onError: console.log,\n });\n });\n \u003C\u002F script >\n Initialize the widget using your API key and the configuration properties. For a detailed list of available properties, refer to the props section in the usage section. Leverage the provided event callbacks, such as onSuccess and onError, to handle claim submission outcomes. For more details on available events, visit the events section in the detailed usage guide. Embedding the Widget To embed the widget on your website or application, you need to add the following HTML code wherever you want the widget to appear: \u003C claims-widget >\u003C\u002F claims-widget >\n Simply include this HTML element in your web page or application code, and the widget will be embedded and displayed in the specified location. html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"id":31,"path":32,"dir":23,"title":33,"description":34,"keywords":35,"body":37},"content:1.guide:what-is-axitech-widget.md","\u002Fguide\u002Fwhat-is-axitech-widget","What is Axitech Widget?","The Axitech Widget is designed to make integrating branded insurance claim experiences into your own web applications easy, while connecting seamlessly to your claims supply chain. This widget offers a comprehensive range of customization options, both visually and functionally, allowing you to tailor user journeys for a variety of motor claim types that fit your precise needs.",[36],"Key Features and Benefits"," What is Axitech Widget? The Axitech Widget is designed to make integrating branded insurance claim experiences into your own web applications easy, while connecting seamlessly to your claims supply chain. This widget offers a comprehensive range of customization options, both visually and functionally, allowing you to tailor user journeys for a variety of motor claim types that fit your precise needs. Key Features and Benefits Seamless Integration: The Axitech Widget seamlessly integrates insurance claim functionalities directly into your web application. This integration ensures a consistent and streamlined user experience, enhancing customer satisfaction. Customizable: With a wide array of configuration properties, the widget can be tailored to match your application's branding and requirements. This customization extends to the claim creation process, ensuring that users feel at ease throughout the journey. Intuitive Design: The widget facilitates a user-friendly experience through supporting pre-populated data from your web application, minimising customer input requirements to allow them to focus on navigating effortlessly through the details that matter. Enhanced User Experience: By leveraging the Axitech Widget, you deliver a superior user experience that aligns seamlessly with both your website and claims systems, while also benefiting from data collection over and above what your existing claims provider may be able to support. This allows users to interact with a modern experience to smoothly initiate and manage insurance claims digitally. Comprehensive Claim Types: The widget can selectively enable or disable a variety of claim types, including accidents, theft, weather damage, and more. This versatility enables you to cater to a wide range of scenarios, ensuring the relevance of digital experiences across various schemes. Secure Initialization: The widget offers multiple initialization methods, including API key-based and secure client ID and web token-based approaches. This flexibility accommodates your security preferences and requirements. Compatibility with the Axitech suite: As can be expected, the Axitech widget has been designed with ultimate compatibility with the Axitech product suite in mind. If your claims operations make use of Axicloud, data collected can be configured to interface with Axicloud seamlessly, allowing a variety of possibilities when it comes to service continuation beyond-FNOL. Incorporating the Axitech Widget into your application empowers you to accelerate digital transformation in claims. By providing users with an intuitive experience out of the box, you can elevate customer satisfaction, reduce claims lifecycle, and establish yourself as a reliable platform for modern insurance.",{"id":39,"path":40,"dir":41,"title":42,"description":43,"keywords":44,"body":47},"content:2.embedded:0.example.md","\u002Fembedded\u002Fexample","embedded","Example","Dive into this comprehensive example that vividly demonstrates how to harness the properties to intricately tailor the app's widget, thus elevating the user experience:",[45,46],"Embedding the Widget","Customized Initialization with Loading Options"," Example Dive into this comprehensive example that vividly demonstrates how to harness the properties to intricately tailor the app's widget, thus elevating the user experience: {\n \"type\" : \"claim\" ,\n \"clientID\" : \"your-client-id\" ,\n \"contact\" : {\n \"phone\" : \"123-456-7890\" ,\n \"email\" : \"contact@example.com\"\n },\n \"policy\" : {\n \"provider\" : \"ABC Insurance\" ,\n \"number\" : \"P12345\" ,\n \"validTo\" : \"2001-01-01\" ,\n \"validFrom\" : \"2000-01-01\" ,\n \"vehicle\" : {\n \"licensePlate\" : \"XYZ-123\"\n },\n \"holder\" : {\n \"phone\" : \"987-654-3210\" ,\n \"email\" : \"user@example.com\" ,\n \"firstName\" : \"John\" ,\n \"lastName\" : \"Doe\"\n },\n \"linkedContacts\" : [\n {\n \"firstName\" : \"Jane\" ,\n \"lastName\" : \"Doe\" ,\n \"email\" : \"jane.doe@test.com\"\n },\n {\n \"firstName\" : \"Test\" ,\n \"lastName\" : \"User\" ,\n \"email\" : \"test@test.com\"\n }\n ]\n },\n \"currentUserId\" : \"user-id\" ,\n \"initialStepKey\" : \"accident-selector\" ,\n \"theme\" : {\n \"primary\" : \"#FF5733\" ,\n \"secondary\" : \"#6C7A89\"\n \u002F\u002F ... other theme properties\n },\n \"fontFamily\" : \"Arial\" ,\n \"privacyPolicyUrl\" : \"https:\u002F\u002Fexample.com\u002Fprivacy-policy\"\n }\n This illustrative example unveils the intricate configuration possibilities achievable through the properties. Spanning from specifying claim types and client identification to seamlessly incorporating contact information and fine-tuning visual aesthetics, these properties empower a tailored and refined user journey. For a comprehensive insight into each property and its nuances, kindly refer to the Widget Properties section above. This segment elaborates on the purpose, usage, and potential of each property, offering you the tools to craft a widget that precisely aligns with your intentions. Embedding the Widget To embed the widget on your website or application, you need to add the following HTML code wherever you want the widget to appear: \u003C claims-widget >\u003C\u002F claims-widget >\n Simply include this HTML element in your web page or application code, and the widget will be embedded and displayed in the specified location. Customized Initialization with Loading Options Empowering you with versatility, our widget presents a sophisticated load function, enabling two distinct methods of initialization that align seamlessly with your needs: API Key-based Initialization: \nEmploy your API key alongside the options JSON object to prime the widget for operation. This method provides direct configuration of the widget. load ( 'API-KEY' , {\n type: 'accident' ,\n clientID: 'your-client-id' ,\n \u002F\u002F ... other properties\n });\n Secure Client ID and Web Token Initialization: \nFor heightened security, utilize your client ID and a JSON web token. Encode the options JSON object using your API key as a secret for encryption. Ensure that you use your API key as the secret for encoding . Notably, the client ID in the options is redundant when using this method, as it is passed as the first parameter so you do not necessarily need to add into options. load ( 'CLIENT-ID' , 'ENCODED-JSON-WEB-TOKEN' , callbacks);\n By harnessing these dynamic methods, you seamlessly integrate the widget, adapting its functionality precisely to your requirements. Secure initialization ensures confidentiality, allowing the widget to elegantly conform to your application's demands. html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"id":49,"path":50,"dir":41,"title":51,"description":52,"keywords":53,"body":55},"content:2.embedded:1.props.md","\u002Fembedded\u002Fprops","Properties","Here is a compilation of properties that empower you to customize the Axitech Widget's functionality. These properties afford you the flexibility to fine-tune the user experience according to your specific requirements.",[54],"Property Details"," Properties Here is a compilation of properties that empower you to customize the Axitech Widget's functionality. These properties afford you the flexibility to fine-tune the user experience according to your specific requirements. Note: properties marked with * are also used in the standalone version of the widget Property Type Description Required type string Specifies the type of claim you want to create. This can be used to preselect a default claim type. Optional clientID string Your unique client ID for authentication and tracking purposes. Required contact * object An object containing contact information for display in the \"Contact Us\" section. Required optional configured based on clintId in the standalone version policy * object An object or an array representing policy information for the claim. Contains holder, vehicle and other relevant policy details. Optional initialStepKey * string Specifies the initial step to start the claim creation process. Optional sessionTracking boolean Enables session tracking to save user progress and reload field values. Optional currentUserId * string The user's unique ID for session tracking. Optional required in the standalone version state object An object that defines the current state of the widget, including various details related to the claim process. Optional privacyPolicyUrl * string Specifies the URL where the privacy policy can be found. Optional theme object Allows customization of the widget's visual appearance, including colors and fonts. Optional, recommended to configure via admin interface fontFamily string Specifies a custom font family to be used throughout the widget. Optional, recommended to configure via admin interface cookie object Controls cookie behavior, including cookie consent, analytics IDs, and OneTrust integration. Optional Property Details type Property This property allows you to specify the type of claim you want to create. By setting this property, you can preselect a default claim type for the user. clientID Property This property requires your unique client ID, which serves for authentication and tracking purposes. The client ID is used to identify and associate claims with your application. contact Object This object contains contact information that will be displayed in the \"Contact Us\" section of the app's widget. The contact details provide users with a way to reach out for assistance and support during the claim creation process. phone (string, required): The contact phone number that users can use to call for support. email (string, required): The contact email address that users can use to email for support. policy Object This object contains insurance-related information that can be associated with the claim. It helps in identifying the insurance provider and policy associated with the claim. provider (string, optional): The name of the insurance provider. number (string, optional): The policy number associated with the claim. validTo (string, optional): The date when the policy expires. validFrom (string, optional): The date when the policy becomes valid. holder Object (optional) This object represents the user who is initiating the claim creation process. It includes various user-related information that can be useful for tracking and communication purposes. phone (string, optional): The user's phone number. email (string, optional): The user's email address. firstName (string, optional): The user's first name. lastName (string, optional): The user's last name. any other user-related information vehicle Object (optional) This object contains details about the vehicle associated with the claim, such as the license plate number. licensePlate (string, optional): The license plate of the vehicle associated to this policy and involved in the claim. any other vehicle-related information linkedContacts Array (optional) This array contains contact information for other individuals associated with the policy. Each entry in the array conforms to the holder object. currentUserId Property This property allows you to specify the user's unique ID for session tracking. This ID is used to identify and associate claims with the user. It is required when sessionTracking is on. initialStepKey Property This property allows you to specify the initial step for the claim creation process. Users will start at this step when they begin creating a claim. The value for this property must be chosen from the following list of valid steps: 'accident-selector' 'single-vehicle-form' 'multiple-vehicle-form' 'windscreen-form' 'theft-claim-selector' 'vehicle-theft-form' 'theft-from-vehicle-form' 'other-claim-selector' 'malicious-damage-form' 'fire-damage-form' 'weather-damage-selector' 'flood-form' 'hail-lightning-form' 'other-weather-damage-form' 'locked-out-form' sessionTracking Property The sessionTracking property, when set to true , enables session tracking within the widget. This feature allows the widget to save a user's progress and reload previously entered field values when they return to the widget, ensuring a seamless and user-friendly experience. Set this property to false if you do not wish to enable session tracking. Enabling session tracking can be particularly useful for improving the user experience and reducing the need for users to re-enter information when interacting with the widget across multiple sessions. state Property The state property allows you to define the current state of the widget, providing detailed information related to the ongoing claim process. This property is an object with various sub-properties that offer a comprehensive view of the claim's status. Let's explore each sub-property: date (string, optional): The date associated with the claim. location ( address , optional): An object describing the location or address related to the claim. It includes properties such as latitude, longitude, formatted address, address lines, city, state, country, and postal code. vehicleRoadWorthy (boolean, optional): Indicates whether the vehicle involved in the claim is roadworthy. driver (boolean, optional): Indicates the presence of a driver in the claim. injured (boolean, optional): Indicates if there are reported injuries associated with the claim. thirdParties (array of contact or thirdPartyDriver , optional): An array containing contact information for third parties involved in the claim. Each entry in the array conforms to the Contact or third party driver object. witnesses (array of contact , optional): An array containing contact information for witnesses present during the claim. Each entry follows the Contact object. reportedToPolice (boolean, optional): Indicates whether the claim has been reported to the police. dashCamFootageAvailable (boolean, optional): Indicates if dashcam footage is available for the claim. notificationTime ( notificationTime , optional): Information about the preferred notification time, including values like 'anytime,' 'morning,' 'afternoon,' and 'evening.' termsAccepted (boolean, optional): Indicates if the terms and conditions have been accepted by the user. policy ( policy , optional): An object representing policy information for the claim. vehicleImages (array of strings, optional): An array of URLs representing images of the vehicle associated with the claim. additionalImages (array of strings, optional): An array of URLs representing additional images related to the claim. note (string, optional): Additional notes or comments related to the claim. stepKey ( initialStepKey , required): Specifies the current step in the claim creation process. The StepKey is selected from a predefined list of options, including 'accident-selector,' 'single-vehicle-form,' 'multiple-vehicle-form,' and more. address Object The Address object defines the structure of an address object, which can be used to represent location-related information associated with a claim. The Address object includes the following properties: latitude (number, required): The latitude coordinate of the address. longitude (number, required): The longitude coordinate of the address. formattedAddress (string, optional): A formatted representation of the address. addressLine1 (string, optional): The first line of the address. addressLine2 (string, optional): The second line of the address. city (string, optional): The city or locality of the address. state (string, optional): The state or region of the address. country (string, optional): The country of the address. postalCode (string, optional): The postal or ZIP code of the address. contact object The Contact object defines the structure of contact information, which can be used to represent individuals involved in a claim. The Contact object includes the following properties: firstName (string, optional): The first name of the contact. lastName (string, optional): The last name of the contact. email (string, optional): The email address of the contact. type (string, required): Specifies the type of contact, which can be one of the following: 'driver,' 'motorcyclist,' 'pedestrian,' 'cyclist,' 'other,' or 'witness.' phone ( phone , optional): An object representing the phone number of the contact. address ( address , optional): An object representing the address of the contact. thirdPartyDriver object The ThirdPartyDriver object extends the Contact object and adds specific information related to a third-party driver involved in a claim. It includes all properties defined in the Contact object and additional properties: vehicle ( vehicle , optional): An object representing vehicle information for the third-party driver. insurance ( insurance , optional): An object representing insurance information for the third-party driver. The ThirdPartyDriver object is used when capturing details about a third-party driver, including their vehicle and insurance information. notificationTime object The NotificationTime object specifies the available options for preferred notification times related to a claim. It includes the following values: anytime : Notifications can be received at any time. morning : Notifications are preferred in the morning. afternoon : Notifications are preferred in the afternoon. evening : Notifications are preferred in the evening. Please Note: If sessionTracking is set to true , the state property will be ignored. The state property offers a comprehensive way to manage and track the progress of a claim within the widget. It allows you to store and retrieve various claim-related information, ensuring a smooth and organized claim creation process. privacyPolicyUrl Property This property allows you to specify the URL where the privacy policy associated with the claims creation process can be found. Providing a valid privacy policy URL ensures transparency and compliance with legal requirements regarding user data and privacy. theme Object (Not Recommended) The theme object allows you to customize the visual appearance of the app's widget. You can modify various visual aspects using color codes and font URLs. primary (string, optional): The primary color used for UI elements. secondary (string, optional): The secondary color used for UI elements. positive (string, optional): The color for positive actions. negative (string, optional): The color for negative actions. fontPrimary (string, optional): The font color used for primary text. fontSecondary (string, optional): The font color used for secondary text. background (string, optional): The background color of the widget. backgroundSoft (string, optional): A softer background color for certain UI elements. borderRadius (string, optional): The border radius for components in the widget. shadow (string, optional): Shadow effect applied to components. primaryBoldUrl (string, optional): URL for a bold primary font. primaryRegularUrl (string, optional): URL for a regular primary font. secondaryBoldUrl (string, optional): URL for a bold secondary font. secondaryRegularUrl (string, optional): URL for a regular secondary font. Please Note: While you have the flexibility to configure the widget's visual appearance through theme-related properties, we highly recommend utilizing our admin interface for theming. The admin interface offers a user-friendly way to configure and manage the widget's theme, providing a more streamlined and efficient process for achieving the desired look and feel of the widget. fontFamily Property (Not Recommended) This property allows you to specify a custom font family to be used throughout the widget. You can set it to any valid font family name. Please Note: While you have the flexibility to configure the widget's font family, we highly recommend utilizing our admin interface for this. The admin interface offers a user-friendly way to configure and manage the widget's fonts.",{"id":57,"path":58,"dir":41,"title":59,"description":60,"keywords":61,"body":63},"content:2.embedded:2.events.md","\u002Fembedded\u002Fevents","Events","Apart from properties, the Axitech Widget also provides events that allow you to seamlessly handle different stages of the widget's lifecycle.",[62],"Event Details"," Events Apart from properties, the Axitech Widget also provides events that allow you to seamlessly handle different stages of the widget's lifecycle. Event Description onSuccess Executes after a claim submission is successfully processed. Provides the submitted data object as a parameter. onError Executes when an error occurs during the claim submission process. Provides an API error as a parameter. onChange Executes when the claim data changes. Provides the updated claim data object as a parameter. Event Details onSuccess Event The onSuccess function is invoked after a claim submission is successfully processed. It provides information related to the submitted claim, including the submission date. You can use this function to perform custom actions or display confirmation messages upon successful claim submission. Example Usage widget. load ( 'API-KEY' , {\n \u002F\u002F ... other configuration properties\n onSuccess : function ( submissionDate ) {\n \u002F\u002F Handle success, e.g., display a success message or perform custom actions.\n console. log ( 'Claim submitted successfully on:' , submissionDate);\n },\n });\n onError Event The onError function is executed when an error occurs during the claim submission process. It provides a custom error message that can help you identify and handle the issue gracefully. You can use this function to display error messages or log error details for further investigation. Example Usage widget. load ( 'API-KEY' , {\n \u002F\u002F ... other configuration properties\n onError : function ( errorMessage ) {\n \u002F\u002F Handle error, e.g., display an error message or log error details.\n console. error ( 'Claim submission error:' , errorMessage);\n },\n });\n onChange Event The onChange event is triggered whenever any data within the widget is changed. It provides information about the specific data that was changed, allowing you to react to data modifications in real-time. Example Usage: widget. load ( 'API-KEY' , {\n \u002F\u002F ... other configuration properties\n onChange : function ( changedData ) {\n \u002F\u002F React to data changes as needed\n console. log ( 'Widget data changed:' , changedData);\n },\n });\n html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"id":65,"path":66,"dir":41,"title":67,"description":68,"keywords":69,"body":71},"content:2.embedded:3.methods.md","\u002Fembedded\u002Fmethods","Methods","In addition to properties and events, the Axitech Widget offers methods that enable dynamic interaction and configuration adjustments.",[70],"Method Details"," Methods In addition to properties and events, the Axitech Widget offers methods that enable dynamic interaction and configuration adjustments. Method Description load Initializes the widget and its configuration using the provided API key and options. applyConfig Dynamically applies configuration changes to the widget after its initialization. Method Details load Method The load method is used to initialize the widget with the provided configuration options. It offers two distinct methods of initialization, providing you with versatile choices for seamless integration based on your requirements. API Key-based Initialization: \nEmploy your API key alongside the options JSON object to prime the widget for operation. This method provides direct configuration of the widget. load ( 'API-KEY' , {\n type: 'accident' ,\n clientID: 'your-client-id' ,\n \u002F\u002F ... other properties\n });\n Secure Client ID and Web Token Initialization: \nFor heightened security, utilize your client ID and a JSON web token. Encode the options JSON object using your API key. Ensure that you use your API key as the secret for encoding . Notably, the client ID in the options is redundant when using this method, as it is passed as the first parameter, so you do not necessarily need to add it to the options. load ( 'CLIENT-ID' , 'ENCODED-JSON-WEB-TOKEN' , callbacks);\n Where callbacks is an optional object containing the following functions: onSuccess : A function to handle successful submission. onError : A function to handle any submission errors. onChange : A function to handle changes in the widget data. For detailed instructions, refer to the Events section This additional parameter is necessary as you can't pass functions directly in a JWT string. By offering multiple initialization methods, the load function empowers you to configure the widget with flexibility and security, ultimately enhancing the claim creation experience for your users. applyConfig Method The applyConfig method provides the capability to dynamically adjust the widget's configuration post-initialization. This dynamic feature enables precise refinement of the widget's behavior as your application evolves. It is important to note that, for security and performance considerations, this function will execute only if the data being submitted differs from the previous submission (if it exists). Additionally, there is a throttle of 500 milliseconds in place to prevent an excessive number of updates. Plain Object Configuration: \nBy utilizing a plain object, you can effortlessly integrate updated configuration options. This method ensures that changes to the widget's behavior take effect immediately. applyConfig ({\n theme: {\n primary: '#FF5733' ,\n secondary: '#6C7A89' ,\n \u002F\u002F ... other theme properties\n },\n \u002F\u002F ... other updated properties\n });\n Web Token Configuration: \nFor heightened security, utilize a JSON web token. You can easily encode the options JSON object using your API key. Ensure that you use your API key as the secret for encoding . This method also ensures that changes to the widget's behavior take effect immediately. applyConfig ( 'ENCODED-JSON-WEB-TOKEN' );\n By utilizing the applyConfig method with plain object configuration, you can seamlessly adjust the widget's behavior in real-time to cater to your evolving application requirements. html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"id":73,"path":74,"dir":41,"title":75,"description":76,"keywords":77,"body":82},"content:2.embedded:6.cookie-config.md","\u002Fembedded\u002Fcookie-config","Cookie Configuration","The Axitech Widget provides comprehensive cookie management capabilities, allowing you to control how cookies are handled within the widget. This is especially important for compliance with privacy regulations like GDPR, CCPA, and others.",[78,79,80,81],"Cookie Configuration Options","Implementation","Passing Consent from Parent Application","Acceptance Criteria"," Cookie Configuration The Axitech Widget provides comprehensive cookie management capabilities, allowing you to control how cookies are handled within the widget. This is especially important for compliance with privacy regulations like GDPR, CCPA, and others. Cookie Configuration Options The cookie configuration object supports the following properties: Property Type Description enabled boolean Master switch for all third-party cookies (GA, Clarity, W3W). When false , no cookies will be set and no requests will be made to these services. gaId string Overrides the default Google Analytics ID. clarityId string Optional Microsoft Clarity tag ID. oneTrustDomainId string OneTrust domain ID for cookie banner integration. Implementation Basic Usage load ( 'your-api-key' , {\n clientId: 'your-client-id' ,\n contact: {\n phone: '0330 058 4077' ,\n email: 'claims@example.com' ,\n },\n cookie: {\n enabled: true , \u002F\u002F Allow cookies\n oneTrustDomainId: 'your-domain-id' , \u002F\u002F OneTrust domain ID\n },\n });\n Inheriting Consent from Parent Domain If your widget is embedded on a page that already has cookie consent management, you can inherit those settings: load ( 'your-api-key' , {\n clientId: 'your-client-id' ,\n \u002F\u002F ...other settings\n cookie: {\n enabled: true ,\n },\n });\n Custom Analytics IDs You can specify custom Google Analytics or Microsoft Clarity IDs: load ( 'your-api-key' , {\n clientId: 'your-client-id' ,\n \u002F\u002F ...other settings\n cookie: {\n enabled: true ,\n gaId: 'UA-CUSTOM-ID' , \u002F\u002F Custom GA ID\n clarityId: 'YOUR-CLARITY-ID' , \u002F\u002F Custom Clarity ID\n },\n });\n Passing Consent from Parent Application The widget provides a function to update cookie consent settings from the parent application: import { updateWidgetCookieConsent } from 'axitech-widget' ;\n \n \u002F\u002F Update analytics consent\n updateWidgetCookieConsent ({\n analytics: true , \u002F\u002F Allow analytics cookies\n });\n \n \u002F\u002F Update multiple consent categories\n updateWidgetCookieConsent ({\n analytics: true , \u002F\u002F Allow analytics cookies\n marketing: false , \u002F\u002F Disallow marketing cookies\n functional: true , \u002F\u002F Allow functional cookies\n });\n This is useful when your main application has its own cookie consent management system, and you want to synchronize settings with the embedded widget. Acceptance Criteria The cookie configuration satisfies the following criteria: When enabled is set to false , no third-party cookies are set, and no requests are made to GA\u002FClarity\u002FW3W. html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"id":84,"path":85,"dir":7,"title":86,"description":87,"keywords":88,"body":91},"content:3.standalone:0.index.md","\u002Fstandalone","Standalone Mode Usage","The Axitech Widget also provides a standalone mode, allowing you to integrate the widget without npm installation. In standalone mode, users need to make an API request to our API, which will generate access URLs for each of your users.",[89,90],"Generating a Standalone Access Link","Example Response"," Standalone Mode Usage The Axitech Widget also provides a standalone mode, allowing you to integrate the widget without npm installation. In standalone mode, users need to make an API request to our API, which will generate access URLs for each of your users. Generating a Standalone Access Link To generate a standalone access link, you need to make an API request to our endpoint. Here is a decription of the api endpoint: POST \u002F:clientId\u002Flink (generates a standalone access link) Parameters name type data type description callbackUrl required string This parameter will be the url where the user will be redirected to after finishing the claim submission callbackOnSubmit optional string This parameter will determine when the user is redirected, if true it will redirect the user immediately after submission without showing the user a success page (false by default) config required Object Similar to Widget Properties accepted by the embedded version of the widget (props marked with * will be available in the standalone version as well) Note: the currentUserId parameter is required in the standalone version Examples \n Typescript import axios, { AxiosResponse } from 'axios' ;\n \n const clientId = 'YOUR_CLIENT_ID' ;\n const apiKey = 'YOUR_API_KEY' ;\n const apiUrl = `https:\u002F\u002Fadmin.axiwidget.io\u002F${ clientId }\u002Flink` ;\n \n const requestBody = {\n callbackUrl: 'https:\u002F\u002Fexample.com\u002Fcallback' ,\n callbackOnSubmit: false ,\n config: {\n \u002F\u002F ... (your widget configuration)\n },\n } satisfies WidgetRequestBody ;\n \n axios\n . post (apiUrl, requestBody, {\n headers: {\n 'x-api-key' : apiKey,\n 'Content-Type' : 'application\u002Fjson' ,\n },\n })\n . then (( response : AxiosResponse \u003C{ data : string }>) => {\n console. log ( 'Access URL:' , response.data.data);\n })\n . catch (( error ) => {\n console. error ( 'Error:' , error.response?.status, '-' , error.response?.data);\n });\n \n interface WidgetRequestBody {\n callbackUrl : string ;\n callbackOnSubmit : boolean ;\n config : {\n contact : {\n email : string ;\n phone : string ;\n link ?: string ;\n };\n currentUserId : string | number ;\n policy ?: {\n provider ?: string ;\n number ?: string ;\n validTo ?: string ;\n validFrom ?: string ;\n holder ?: {\n firstName ?: string ;\n lastName ?: string ;\n email ?: string ;\n phone ?: string ;\n };\n vehicle ?: {\n licensePlate ?: string ;\n };\n linkedContacts ?: {\n firstName ?: string ;\n lastName ?: string ;\n email ?: string ;\n phone ?: string ;\n }[];\n };\n initialStepKey ?: StepKey ;\n privacyPolicyUrl ?: string ;\n };\n }\n \n PHP Laravel use Illuminate\\Support\\Facades\\Http ;\n \n $clientId = 'YOUR_CLIENT_ID' ;\n $apiKey = 'YOUR_API_KEY' ;\n $apiUrl = \"https:\u002F\u002Fadmin.axiwidget.io\u002F{ $clientId }\u002Flink\" ;\n \n $requestBody = [\n 'callbackUrl' => 'https:\u002F\u002Fexample.com\u002Fcallback' ,\n 'callbackOnSubmit' => false ,\n 'config' => [\n \u002F\u002F ... (your widget configuration)\n ],\n ];\n \n $response = Http :: withHeaders ([\n 'x-api-key' => $apiKey,\n 'Content-Type' => 'application\u002Fjson' ,\n ]) -> post ($apiUrl, $requestBody);\n \n if ($response -> successful ()) {\n $responseData = $response -> json ();\n echo 'Access URL: ' . $responseData[ 'data' ];\n } else {\n echo 'Error: ' . $response -> status () . ' - ' . $response -> body ();\n }\n In the example above: Replace clientId in the URL with your actual client ID.\nReplace YOUR_API_KEY in the x-api-key header with your actual API key.\nThe API will respond with an access URL that users can use to access the standalone version of the Axitech Widget. Example Response {\n \"data\" : \"https:\u002F\u002Fadmin.axiwidget.io\u002Fverify\u002FACCESS_CODE?token=ENCODED_TOKEN\"\n }\n Users can open this URL in their web browser to access the standalone version of the Axitech Widget. For additional details on the widget properties and customization options, refer to the Widget Properties section in the documentation. That's it! You've successfully integrated the standalone version of the Axitech Widget into your application using API requests. html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"id":93,"path":94,"dir":95,"title":96,"description":97,"keywords":98,"body":101},"content:3.standalone:1.sessions.md","\u002Fstandalone\u002Fsessions","standalone","Session Listing","The Session Listing functionality allows you to retrieve information about user sessions made through the Axitech Widget.",[99,100],"Response","Error Responses"," Session Listing The Session Listing functionality allows you to retrieve information about user sessions made through the Axitech Widget. GET \u002F:clientId\u002Fsessions\u002F:userId (list sessions created by a user) Path Parameters name type data type description clientId required string Your unique client ID userId required string The unique ID of the user for whom you want to retrieve session listings Examples \n Typescript import axios, { AxiosResponse } from 'axios' ;\n \n const clientId = 'YOUR_CLIENT_ID' ;\n const apiKey = 'YOUR_API_KEY' ;\n const userId = 'USER_ID' ; \u002F\u002F Replace with the actual user ID\n const apiUrl = `https:\u002F\u002Fadmin.axiwidget.io\u002F${ clientId }\u002Fsessions\u002F${ userId }` ;\n \n axios\n . get (apiUrl, {\n headers: {\n 'x-api-key' : apiKey,\n 'Content-Type' : 'application\u002Fjson' ,\n },\n })\n . then (( response : AxiosResponse \u003C{ data : Session [] }>) => {\n console. log ( 'Session Listings:' , response.data);\n })\n . catch (( error ) => {\n console. error ( 'Error:' , error.response?.status, '-' , error.response?.data);\n });\n \n interface Session {\n reference : string ;\n date : string ;\n camsReference : string ;\n status : string ;\n createdAt : string ;\n selectedPolicy : {\n number : string ;\n provider : string ;\n holder : {\n firstName : string ;\n lastName : string ;\n id : string ;\n phone : string ;\n email : string ;\n };\n validFrom : string ;\n linkedContacts : {\n firstName : string ;\n lastName : string ;\n email : string ;\n }[];\n validTo : string ;\n vehicle : {\n sePlate : string ;\n };\n };\n }\n \n PHP Laravel use Illuminate\\Support\\Facades\\Http ;\n \n $clientId = 'YOUR_CLIENT_ID' ;\n $apiKey = 'YOUR_API_KEY' ;\n $userId = 'USER_ID' ; \u002F\u002F Replace with the actual user ID\n $apiUrl = \"https:\u002F\u002Fadmin.axiwidget.io\u002F{ $clientId }\u002Fsessions\u002F{ $userId }\" ;\n \n $response = Http :: withHeaders ([\n 'x-api-key' => $apiKey,\n 'Content-Type' => 'application\u002Fjson' ,\n ]) -> get ($apiUrl);\n \n if ($response -> successful ()) {\n $responseData = $response -> json ();\n echo 'Session Listings: ' . json_encode ($responseData, JSON_PRETTY_PRINT );\n } else {\n echo 'Error: ' . $response -> status () . ' - ' . $response -> body ();\n }\n Response The response contains an array of session details. Session Details reference (string): A unique reference ID for the session. date (string, ISO 8601 format): The date and time of the session. camsReference (string): Reference ID used in CAMS. status (string): The status of the session (e.g., \"submitted\"). createdAt (string, ISO 8601 format): The date and time when the session was created. selectedPolicy (object): Details about the selected insurance policy.\n number (string): The policy number. provider (string): The insurance provider. holder (object): Details about the policyholder.\n firstName (string): First name of the policyholder. lastName (string): Last name of the policyholder. id (string): ID of the policyholder. phone (string): Phone number of the policyholder. email (string): Email address of the policyholder. validFrom (string, ISO 8601 format): The start date of the policy's validity. linkedContacts (array): Contacts linked to the policy.\n firstName (string): First name of the linked contact. lastName (string): Last name of the linked contact. email (string): Email address of the linked contact. validTo (string, ISO 8601 format): The end date of the policy's validity. vehicle (object): Details about the vehicle associated with the policy.\n licensePlate (string): License plate number of the vehicle. Example Response [\n {\n \"reference\" : \"LA-PE2VZ7RJD4\" ,\n \"date\" : \"2023-11-27T14:52\" ,\n \"camsReference\" : \"MIS\u002F709006\" ,\n \"status\" : \"submitted\" ,\n \"createdAt\" : \"2023-11-27T14:52\" ,\n \"selectedPolicy\" : {\n \"number\" : \"123456\" ,\n \"provider\" : \"Alliance\" ,\n \"holder\" : {\n \"firstName\" : \"Test\" ,\n \"lastName\" : \"User\" ,\n \"id\" : \"test\" ,\n \"phone\" : \"+4917123456789\" ,\n \"email\" : \"test@test.com\"\n },\n \"validFrom\" : \"2023-10-01\" ,\n \"linkedContacts\" : [\n {\n \"firstName\" : \"John\" ,\n \"lastName\" : \"Doe\" ,\n \"email\" : \"john.doe@test.com\"\n },\n {\n \"firstName\" : \"Jane\" ,\n \"lastName\" : \"Doe\" ,\n \"email\" : \"jane.doe@test.com\"\n }\n ],\n \"validTo\" : \"2024-02-15\" ,\n \"vehicle\" : {\n \"licensePlate\" : \"ABC123\"\n }\n }\n }\n \u002F\u002F ... additional sessions\n ]\n Error Responses HTTP 404 Not Found: If the specified client ID is not found. HTTP 401 Unauthorized: If the provided API key is invalid or unauthorized. HTTP 500 Internal Server Error: If there is an unexpected error on the server. html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"id":103,"path":104,"dir":95,"title":105,"description":106,"keywords":107,"body":110},"content:3.standalone:2.webhooks.md","\u002Fstandalone\u002Fwebhooks","Webhooks setup","To integrate webhook events into your application, follow these steps:",[108,109],"The Event Object","Implementation Example:"," Webhooks setup To integrate webhook events into your application, follow these steps: Create Webhook Endpoint : Develop an HTTP endpoint to receive POST requests containing webhook events. Register Endpoint : Register your endpoint with the widget the admin page. Secure Endpoint : Implement request verification to ensure that incoming requests are from the Axitech Widget Webhook Service. Handling Events : Process the received webhook events based on the payload provided in the request body. Return Success Code : Return a 2XX status code upon successful receipt of the event to acknowledge receipt and prevent retries (make sure the endpoint operations are idempotent and accidental retries\u002Fduplications do not break your logic). The Event Object Properties: created_at : string Timestamp indicating when the event was created. Format: 'YYYY-MM-DDTHH:mm:ss'. api_version : string Version of the Axitech Widget Webhook Service API. group_type : string Specifies the group that the specific event belongs to. (e.g., \"WidgetEvent\"). event_type : string Type of the event inside the specified group (e.g., \"submission.created\"). data : object Specific data related to the event. The structure depends on the event type. The session.submitted Event sessionId : string Unique identifier for the session. date : string Timestamp indicating the claim date for example the time of accident if the session is an accident claim. Format: 'YYYY-MM-DDTHH:mm:ss'. integrations : array of objects List of integrations associated with the session.\n key : string Integration key. id : string Unique identifier for the integration. reference : string Reference identifier for the integration. name : string Name of the integration. status : string Status of the integration (e.g., \"success\"). meta : object Additional metadata related to the session. Basically everything that was sent as a request when creating the session Example: Full Payload Example: {\n \"created_at\" : \"2023-01-01T12:00:00Z\" ,\n \"api_version\" : \"v1\" ,\n \"group_type\" : \"WidgetEvent\" ,\n \"event_type\" : \"session.submitted\" ,\n \"data\" : {\n \"sessionId\" : \"52nmBydtBQpGYjXGWXu3\" ,\n \"date\" : \"2023-01-01T12:00:00Z\" ,\n \"integrations\" : [\n {\n \"key\" : \"brokerDirect\" ,\n \"id\" : \"750800\" ,\n \"reference\" : \"MIS\u002F708194\" ,\n \"name\" : \"Broker Direct\" ,\n \"status\" : \"success\"\n }\n ],\n \"meta\" : {\n \u002F\u002F everything that was sent as a request when creating the session\n \"contact\" : {\n \"phone\" : \"123-456-7890\" ,\n \"email\" : \"contact@example.com\"\n },\n \"policy\" : {\n \"provider\" : \"ABC Insurance\" ,\n \"number\" : \"P12345\" ,\n \"validTo\" : \"2001-01-01\" ,\n \"validFrom\" : \"2000-01-01\" ,\n \"vehicle\" : {\n \"licensePlate\" : \"XYZ-123\"\n },\n \"holder\" : {\n \"phone\" : \"987-654-3210\" ,\n \"email\" : \"user@example.com\" ,\n \"firstName\" : \"John\" ,\n \"lastName\" : \"Doe\"\n },\n \"linkedContacts\" : [\n {\n \"firstName\" : \"Jane\" ,\n \"lastName\" : \"Doe\" ,\n \"email\" : \"jane.doe@test.com\"\n },\n {\n \"firstName\" : \"Test\" ,\n \"lastName\" : \"User\" ,\n \"email\" : \"test@test.com\"\n }\n ]\n },\n \"currentUserId\" : \"test-123\" ,\n \"privacyPolicyUrl\" : \"https:\u002F\u002Fexample.com\u002Fprivacy-policy\"\n }\n }\n }\n Implementation Example: const crypto = require ( 'crypto' );\n const express = require ( 'express' );\n \n const API_SECRET = 'wh_sec_YOUR_WEBHOOK_SECRET' ;\n \n const app = express ();\n \n app. use (\n express. json ({\n verify : ( req , res , buffer ) => {\n req.rawBody = buffer;\n },\n })\n );\n \n app. post ( '\u002F' , ( req , res ) => {\n const signature = generateSignature (req.method, req.url, req.headers[ 'x-aw-timestamp' ], req.rawBody);\n \n if (signature !== req.headers[ 'x-aw-signature' ]) {\n return res. sendStatus ( 401 );\n }\n \n console. log ( 'Received webhook' , req.body);\n res. sendStatus ( 200 );\n });\n \n app. listen ( 9000 , () => console. log ( 'Node.js server started on port 9000.' ));\n \n function generateSignature ( method , url , timestamp , body ) {\n const hmac = crypto. createHmac ( 'SHA256' , API_SECRET );\n \n hmac. update ( `${ method . toUpperCase () }${ url }${ timestamp }` );\n \n if (body) {\n hmac. update (body);\n }\n \n return hmac. digest ( 'hex' );\n }\n This Node.js example demonstrates how to create an HTTP endpoint to receive webhook events, verify the request signature, process the event payload, and respond with a success status code. Now you're ready to receive Axitech Widget Webhook Events in your app! 🚀 html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"id":112,"path":113,"dir":7,"title":114,"description":7,"keywords":115,"body":116},"content:4.demo.md","\u002Fdemo","Interactive Demo",[]," Interactive Demo ",{"id":118,"path":119,"dir":7,"title":120,"description":7,"keywords":121,"body":128},"content:CHANGELOG.md","\u002Fchangelog","Changelog",[122,123,122,123,124,125,126,127],"Bug Fixes","Features","1.25.3 (2026-02-23)","1.25.2 (2026-01-27)","1.25.1 (2025-10-02)","1.12.3 (2024-04-08)"," Changelog 1.27.0 (2026-06-08) Bug Fixes AVP-10293: always initialise PostHog in cookieless mode before consent is granted ( 0141e68 ) claims-widget: add sentry error tracking for recaptcha and submission failures ( 8fc1e77 ) claims-widget: allow contact info step when default contact information is configured ( 1123f51 ) claims-widget: simplify recaptcha check to only verify key availability ( 84971be ) deps: add overrides to resolve transitive Dependabot vulnerabilities (AVP-10178) ( 30ba86b ) deps: update docs package overrides to resolve transitive vulnerabilities (AVP-10178) ( 72813a1 ) deps: update vulnerable packages (AVP-10178) ( f57b4e6 ) Features claims-widget: add posthog event tracking for recaptcha and submission outcomes ( 853a042 ) 1.26.0 (2026-05-26) Bug Fixes AVP-10047: align email and phone validation with backend ( cdac05b ) AVP-10245: hide card title on non-default themes when no images are present ( 8d5d8d0 ) AVP-9041 Fix recaptcha timeout issues and remove V2 recaptcha ( 60db2d1 ) AVP-9440 Resolve circular dependency ( 772db08 ) AVP-9440 Resolve circular dependency ( f8523b2 ) AVP-9440 Resolve circular dependency ( 6d8bcb7 ) AVP-9470 Fixed after description section when only a single brand is specified ( 341d83d ) AVP-9969 Widget Fix issue where going back on referral does not deselect the brand selected phones lines ( 05040b9 ) Fix external tooltip library css loading issue ( 822e6ff ) Fix jeep referral styling ( a5b8322 ) fix phone input version ( 8a75867 ) Fix report another not resetting to first step when progress tracking is enabled ( 7bda58b ) Fix url construction error ( f14c28c ) improve formrenderer skeleton flashing ( 784b0f6 ) load floating ui style raw ( 5c76536 ) remove background and hover styles from widget form elements ( ad7328a ) remove submit arrow on volvo ( db9a48b ) remove unused files ( 8aa4feb ) replace console.log with console.error in request error handler ( 38f3d07 ) revert phone input version that breaks input ( 30e1591 ) solved wrong html tag being used for skeleton ( fd7648a ) speed up pre-commit hook with lint-staged and skip npm install ( 5385a3f ) Use correct staging ssm path ( 21e236b ) Features AVP-8765 Add itas capture widget support ( 20e4099 ) AVP-9039 Sets brand if there is only one option so that contact info is shown by default on referral ( 1727b26 ) AVP-9173 Mazda Widget Update Mazda widget button styling ( 2a63b34 ) Add common styling to support description with proper spacing ( 79f4100 ) Add gitkeep ( 3d8ec69 ) Add improved skeleton loaders for dynamic imports ( c9d9c1c ) add kia referral form support ( 25d186a ) Add scrolling to back button when landing on ( dc5e70f ) Add staging widget ( 3dc4ecc ) Add support for agent details description ( a1cf3bc ) Add tooltips to back btn and progress indicators ( fe0621a ) AVP-10082: replace navigateTo helper with native anchor tag attributes ( 50215eb ) AVP-8045 Make widget available on staging and move current dev domain to staging. ( be60095 ) AVP-8117 Build FE solution to allow sharing client a page to spoof crash advisor sessions during client integration ( 356bb17 ) AVP-9408 SECOPS Update and document vulnerabilities on axitech widget ( b56aff7 ) AVP-9412 Add referral step progress bar ( d30c01e ) AVP-9439 Add correct conditional form input validation ( 10efe07 ) AVP-9439 AVP-9449 Add referral v3 capabilities and error handling ( 35aadca ) AVP-9440 Add all logos for stellantis ( 2489091 ) AVP-9470 Implement new footer wording per brand for bosch v3 referral ( 67d5dd9 ) AVP-9471 Implement configurable widget localisation ( d198610 ) AVP-9701 Widget Admin panel - blackboxing and securing behind VPC ( 1d2e882 ) AVP-9731 add PostHog events matching GA step_change coverage ( 22b84e9 ) AVP-9731 add PostHog product analytics to widget ( 25781ba ) AVP-9966 add Hyundai and Genesis brand support ( 75aaa30 ) AVP-9975 HMUK RFP Update retailer referral form dropdown copy for Accident Aftercare step ( a6a077d ) AVP-9982 update header logo configuration and sizing ( e53edc3 ) AVP-9983 refactor section header margin syntax ( cd8572d ) AVP-9983 remove bottom margin from Volvo section headers ( fd65292 ) AVP-9983 update section header spacing logic ( 73d7009 ) CA demo integration error handling ( 6eae0fa ) implement vertical referral progress tracker with expandable details ( 4505ace ) Improve code splitting ( ea182d2 ) Support html emergency links ( e437685 ) Update dependencies to latest non-breaking version ( 65d4858 ) Update dependencies to latest non-breaking version ( ce4e7ce ) Update referral progress to only up to current step ( 4454f6d ) update types ( 5d37ab0 ) 1.25.3 (2026-02-23) Bug Fixes AVP-9041 Fix recaptcha timeout issues and remove V2 recaptcha ( 951d6fe ) 1.25.2 (2026-01-27) Bug Fixes AVP-9388 FE Widget Customer 'CollisionCapture' Self Service Implement FE validation when driver and account contact phone numbers are the entered as the same so the system doesnt error out on submission ( 2f45b7a ) 1.25.1 (2025-10-02) Bug Fixes AVP-10245: hide card title on non-default themes when no images are present ( 8d5d8d0 ) 1.26.0-staging.17 (2026-05-20) Bug Fixes AVP-10047: align email and phone validation with backend ( cdac05b ) 1.26.0-staging.16 (2026-05-13) Bug Fixes replace console.log with console.error in request error handler ( 38f3d07 ) speed up pre-commit hook with lint-staged and skip npm install ( 5385a3f ) Features AVP-10082: replace navigateTo helper with native anchor tag attributes ( 50215eb ) 1.26.0-staging.15 (2026-04-29) Features AVP-9731 add PostHog events matching GA step_change coverage ( 22b84e9 ) AVP-9731 add PostHog product analytics to widget ( 25781ba ) 1.26.0-staging.14 (2026-04-24) Bug Fixes remove background and hover styles from widget form elements ( ad7328a ) 1.26.0-staging.13 (2026-04-20) Features AVP-9983 refactor section header margin syntax ( cd8572d ) AVP-9983 remove bottom margin from Volvo section headers ( fd65292 ) 1.26.0-staging.12 (2026-04-19) Features AVP-9983 update section header spacing logic ( 73d7009 ) 1.26.0-staging.11 (2026-04-16) Features AVP-9982 update header logo configuration and sizing ( e53edc3 ) 1.26.0-staging.10 (2026-04-14) Features AVP-9975 HMUK RFP Update retailer referral form dropdown copy for Accident Aftercare step ( a6a077d ) 1.26.0-staging.9 (2026-04-13) Bug Fixes AVP-9969 Widget Fix issue where going back on referral does not deselect the brand selected phones lines ( 05040b9 ) Features AVP-9966 add Hyundai and Genesis brand support ( 75aaa30 ) 1.26.0-staging.8 (2026-03-18) Bug Fixes Fix external tooltip library css loading issue ( 822e6ff ) improve formrenderer skeleton flashing ( 784b0f6 ) load floating ui style raw ( 5c76536 ) solved wrong html tag being used for skeleton ( fd7648a ) Features Add improved skeleton loaders for dynamic imports ( c9d9c1c ) Add scrolling to back button when landing on ( dc5e70f ) Add tooltips to back btn and progress indicators ( fe0621a ) implement vertical referral progress tracker with expandable details ( 4505ace ) Improve code splitting ( ea182d2 ) Update referral progress to only up to current step ( 4454f6d ) 1.26.0-staging.7 (2026-03-04) Bug Fixes Fix url construction error ( f14c28c ) Features AVP-9701 Widget Admin panel - blackboxing and securing behind VPC ( 1d2e882 ) 1.26.0-staging.6 (2026-03-04) Bug Fixes Fix report another not resetting to first step when progress tracking is enabled ( 7bda58b ) Features AVP-9412 Add referral step progress bar ( d30c01e ) 1.26.0-staging.5 (2026-02-06) Bug Fixes remove submit arrow on volvo ( db9a48b ) 1.26.0-staging.4 (2026-02-05) Features update types ( 5d37ab0 ) 1.26.0-staging.3 (2026-02-04) Bug Fixes fix phone input version ( 8a75867 ) revert phone input version that breaks input ( 30e1591 ) 1.26.0-staging.2 (2026-02-04) Features Update dependencies to latest non-breaking version ( 65d4858 ) Update dependencies to latest non-breaking version ( ce4e7ce ) 1.26.0-staging.1 (2026-02-03) Bug Fixes AVP-9041 Fix recaptcha timeout issues and remove V2 recaptcha ( 60db2d1 ) AVP-9388 FE Widget Customer 'CollisionCapture' Self Service Implement FE validation when driver and account contact phone numbers are the entered as the same so the system doesnt error out on submission ( 2f45b7a ) AVP-9440 Resolve circular dependency ( 772db08 ) AVP-9440 Resolve circular dependency ( f8523b2 ) AVP-9440 Resolve circular dependency ( 6d8bcb7 ) AVP-9470 Fixed after description section when only a single brand is specified ( 341d83d ) Fix jeep referral styling ( a5b8322 ) remove unused files ( 8aa4feb ) Use correct staging ssm path ( 21e236b ) Features AVP-8765 Add itas capture widget support ( 20e4099 ) AVP-9039 Sets brand if there is only one option so that contact info is shown by default on referral ( 1727b26 ) AVP-9173 Mazda Widget Update Mazda widget button styling ( 2a63b34 ) Add common styling to support description with proper spacing ( 79f4100 ) Add gitkeep ( 3d8ec69 ) add kia referral form support ( 25d186a ) Add staging widget ( 3dc4ecc ) Add support for agent details description ( a1cf3bc ) AVP-8045 Make widget available on staging and move current dev domain to staging. ( be60095 ) AVP-8117 Build FE solution to allow sharing client a page to spoof crash advisor sessions during client integration ( 356bb17 ) AVP-9408 SECOPS Update and document vulnerabilities on axitech widget ( b56aff7 ) AVP-9439 Add correct conditional form input validation ( 10efe07 ) AVP-9439 AVP-9449 Add referral v3 capabilities and error handling ( 35aadca ) AVP-9440 Add all logos for stellantis ( 2489091 ) AVP-9470 Implement new footer wording per brand for bosch v3 referral ( 67d5dd9 ) AVP-9471 Implement configurable widget localisation ( d198610 ) CA demo integration error handling ( 6eae0fa ) Support html emergency links ( e437685 ) 1.25.0-staging.3 (2025-07-22) Bug Fixes Fix loqate get by id request referer ( e2a740c ) 1.25.0-staging.2 (2025-07-21) Bug Fixes Address search not closing overlay when selecting google result ( f26534b ) Fix referrer policy for loqate request ( e831e22 ) Make sure openreplay is only loaded once ( d9c731b ) Send correct referrer header ( 9c5c95a ) Use fetch referrer instead of explicit header ( 3d92711 ) Features Add cookie settings to widget ( 27b51dd ) Add loqate address search ( 5c9c6b7 ) Add openreplay ( 80c5ff9 ) AVP-8277 Add common theme with Omoda as base design ( df2bd9c ) Ensure to only load analytics scripts when cookies are accepted ( a4424b6 ) Send referer header to loqate requests ( 69cc9ab ) Updates claims widget theme and icons for common theme to support variable brands ( 7601089 ) 1.25.0-staging.1 (2025-06-03) Bug Fixes Correctly set driver status ( e2f2beb ) Fix contact info card to also load config contact info ( 8feb563 ) Fix loading time issue ( a1af6b2 ) Fix suzuki styles not including necessary extend ( 995a80d ) Fix widget context loading issue ( 2d02df6 ) Fixed google map marker placement precision issues ( 2f684c6 ) Revert breaking widget loading issues ( fde57e7 ) Use correct staging ssm path ( 21e236b ) Features Add AA styles and assets ( d2e7c8c ) Add last step styling for suzuki ( 9a13fab ) Add staging widget ( 3dc4ecc ) Add suzuki design ( 17e1707 ) Enhances widget initialization and loading ( 5324ecf ) Improve build process and asset bundling ( 35aa6d4 ) Improve the styling of the context step component ( 5efeed5 ) Initializes Google Maps API only once ( acd00b6 ) Match figma design of AA widget ( 3657f50 ) Update button stylings to better match figma ( 65b5c5b ) 1.24.0-staging.3 (2025-05-28) Bug Fixes Fix loading time issue ( a1af6b2 ) Fix suzuki styles not including necessary extend ( 995a80d ) Fix widget context loading issue ( 2d02df6 ) Revert breaking widget loading issues ( fde57e7 ) Features Add AA styles and assets ( d2e7c8c ) Hide ArcId field on JLR RSA option ( ab22c0f ) Match figma design of AA widget ( 3657f50 ) Update button stylings to better match figma ( 65b5c5b ) Reverts Revert \"Merge branch 'widget-optimizations' into dev\" ( 8336c21 ) 1.24.0-staging.2 (2025-05-21) Bug Fixes Fix string input not loading stored session state ( cd42b07 ) 1.24.0-staging.1 (2025-05-12) Bug Fixes Correctly set driver status ( e2f2beb ) Fix contact info card to also load config contact info ( 8feb563 ) Fixed google map marker placement precision issues ( 2f684c6 ) Use correct staging ssm path ( 21e236b ) Features Add last step styling for suzuki ( 9a13fab ) Add staging widget ( 3dc4ecc ) Add suzuki design ( 17e1707 ) Enhances widget initialization and loading ( 5324ecf ) Improve build process and asset bundling ( 35aa6d4 ) Improve the styling of the context step component ( 5efeed5 ) Initializes Google Maps API only once ( acd00b6 ) 1.22.0-staging.2 (2025-04-28) Bug Fixes Use correct staging ssm path ( 21e236b ) 1.22.0-staging.1 (2025-04-28) Bug Fixes Add \"*\" to all the required fields when adding driver details ( f9b6318 ) AVP-7992 When standalone first loads, there is a period where phone number doesnt display ( ff29830 ) dont call ga if not initialised properly ( 7fa55ce ) Fix ghost btn bg color ( 0ddbcae ) Fix repair finder url ( 8534e3c ) Fix volvo confirm modal btn colors ( 032910a ) Fixed contact information wrongly displayed on claim type widgets ( 88c2eb3 ) Improves reference retrieval logic ( 7309642 ) Make sure to have values for postal code even when the location is a plus code one ( 920ab35 ) Refactors contact info handling for widget ( 85b96e5 ) Repair finder asking for location on render ( ef43317 ) Tesla image section title not appearing ( f429dd8 ) Update lock file ( 2384b81 ) Updates filename encoding for broader compatibility ( 7359313 ) Features Add brand filtering to repair location finder ( 9287aec ) Add cinch icons ( eda3c47 ) Add cinch stylesheets ( d78fd32 ) Add crashdaddy styling to photos modal ( d73c411 ) Add custom tesla form ( 1a8f3e3 ) Add file upload to same s3 as axicloud ( d18df69 ) Add hold to increase\u002Fdecrease to stepper number input ( 10fbb99 ) Add IP and geo location cache ( aa774cf ) Add jlr-referral-v3 form with ArcTwinID input ( 6de7fc8 ) Add last step styling for suzuki ( 9a13fab ) Add preferred country list to phone input ( ee79ec9 ) Add repair finder initial setup ( 6e88ff1 ) Add repair finder map and markers and seach functionality ( 5a50d5a ) Add repair finder with no details overlay ( 142430a ) Add repair location finder optimizations around loading time and shown info ( ad5b6d5 ) Add repair location selector to FNOL widget ( 86c545f ) Add staging widget ( 3dc4ecc ) Add stepper number input for passenger count ( 064d9e6 ) Add suzuki design ( 17e1707 ) Add tesla widget fonts ( 5e2416e ) Add tesla widget icons and other assets from figma ( 38e2012 ) Add toyota styling UK for claims and referral ( db225f8 ) Add toyota v2 us variant and remove Call System References ( 6ee4bbc ) add toyota widget ( 9cda5bc ) Add volvo copy changes ( cdfee56 ) Add volvo wrench icon ( 6b5eb52 ) Add w3w search to google map ( 0595706 ) Added JLR V2 referral form ( 993fad5 ) Change Jagura headings to use the secondary font and reduce font size ( 46827c4 ) copy changes for confirm step ( 02a055c ) Fix contact info being unpopulated on submission ( f64ffe2 ) Implement crashdaddy styling ( e9fab81 ) Implement tesla styling ( 51a81a7 ) Improve the styling of the context step component ( 5efeed5 ) Improvements to button interactions and design ( 217211e ) JLR Self service widget UI improvements following feedback from JLR brand team ( 8a20d26 ) Make repair location card appear in confirm step ( 99f1d02 ) Make volvo ax form feel more reflecting of brand ( f21ed08 ) Preload repair locations based on IP or incident location ( 737d5ff ) The X button should not cancel the upload from the second step of image upload ( 6f45575 ) Update component code to reflect cinch styling ( a9cfb5b ) Update toogle btn and repair card to not have phones ( 190f18e ) 1.20.0-beta.3 (2024-11-28) Features Add hold to increase\u002Fdecrease to stepper number input ( 10fbb99 ) Add stepper number input for passenger count ( 064d9e6 ) 1.20.0-beta.2 (2024-11-22) Features Add custom tesla form ( 1a8f3e3 ) Fix contact info being unpopulated on submission ( f64ffe2 ) 1.20.0-beta.1 (2024-11-21) Bug Fixes Fix sapcing issues ( 0688d8a ) Features Add tesla widget fonts ( 5e2416e ) Add tesla widget icons and other assets from figma ( 38e2012 ) Implement tesla styling ( 51a81a7 ) 1.19.0 (2024-11-14) Bug Fixes Fix feature flag fro clarity throwing error ( f816d68 ) Use param store for build env ( e926c49 ) Features Add ip to statistics sending ( 3264a3c ) 1.18.0 (2024-10-31) 1.17.0 (2024-10-28) Fix date time picker indicator not being correctly displayed on firefox ( bb3ca56 ) Features Add date format that matches what is displayed in the date input ( d93d9af ) 1.17.0 (2024-10-28) Bug Fixes fix issue with jwt token initialisation ( c391a3f ) Fix lead btn condition when lead submission is not successful ( 545a092 ) Features Add acall and bentley widget options ( e992368 ) Replace Customer claims reference with axilcoud lead reference on confirm step for referral submissions ( 9e63089 ) Update axicloud lead btn for JLR ( c94683c ) 1.16.0 (2024-10-14) Features Update recaptcha key ( 4a4033c ) 1.15.0 (2024-10-14) Bug Fixes Add correct analytics keys ( 02b35de ) Add correct label options to radio group with notes ( b493722 ) Bring contact details fields up to style standards ( bd22756 ) Bring input error state to common spec ( ae42df0 ) Change labels to primary text color on bmw design ( f2b6032 ) Contact info card design ( 83453c4 ) Do not ask for recaptcha when not provided in env ( 0376a39 ) Fix aa styling ( 6e966b7 ) Fix add correct clientname to welcome step ( b8315d9 ) Fix axicloud lead submission not rendering correctly on referrals ( c8eef07 ) Fix build type errors ( e0726e5 ) Fix config merging issue ( e95fa12 ) Fix confirm step too many phone numbers with wrong conditions ( 580b16b ) Fix contact info card on mercedes theme ( a80c50f ) Fix contact info input on referral ( d3b7e1d ) Fix context selector state resetting on back ( c1cd379 ) fix date picker range validation ( aa4b631 ) Fix date-time input picker activator size ( 8aa1744 ) Fix default location label ( 6d63630 ) Fix Ecall icon path ( 05aab36 ) Fix external error message not triggering phone input error state ( cf0d958 ) Fix form title casing ( 233ca46 ) Fix google maps usability issues ( 8135e7f ) Fix gutter on desktop overlays ( 44f9c19 ) Fix high severity vulnerabilities ( 65cdffc ) Fix horizontal overflow on standalone widget pages ( 0911074 ) Fix husky config ( b1e1a4d ) Fix incorrect error icon for certain themes ( 7458583 ) Fix input error state icon ( 7559b2d ) Fix insurance fields showing up in non insured forms ( 46c222c ) Fix insurance flags ( 8aefdf4 ) Fix insured flag condition ( e814e09 ) Fix jlr styling ( c9ced59 ) Fix label issues ( 450a5b3 ) Fix load analytics only when key is in env ( 2d42927 ) Fix long loading times for google maps map when fallback to ip location on first load ( 7d07001 ) Fix main title not resetting correctly ( 783e972 ) Fix map height on some mobile devices being wrong ( fed7467 ) Fix overall spacing discrepancies ( 9fc4007 ) Fix overlay alignment ( cef134d ) Fix radio group with note input field triggering invalid form ( 3a3482d ) Fix refer another styling on confirm step ( c5f99f6 ) Fix referral issues ( d5b184b ) Fix referral theme button casing ( 717a712 ) Fix single context not being automatically selected ( 85382d4 ) Fix submit page and contact card spacing ( dacabb7 ) Fix text styling on certain description texts ( 27cb679 ) Fix title alignment on step selector ( c82101f ) Fix tuple component description font ( ef15ad5 ) Fix type error on build ( 7292856 ) Fix type issue ( e367cb7 ) Fix validation required error message ( bdca755 ) Fix volvo contact info card description border ( 415329b ) Fix warning in console when opening overlays ( d812659 ) Fix wrong submission reference on confirm step ( f995d0f ) Google map trigger geolocation when an address was selected from autocomplete, make more accurate search ( 99a3010 ) Improve phone fields to use separate country code and phone number ( 247a969 ) Inconsistent spacing for VW AX and improve welcome page and icons ( 501159a ) Jaguar heading styling ( 67ebb4c ) Make sure copy icon shows only on the clicked item ( 310d579 ) Missing title on ax case form ( fabde61 ) Moved wrong devdependency to dependencies ( cdfc9d4 ) Phone input label usability issue ( 44169fa ) Remove multiple phone inputs ( da91016 ) Remove unnecessarry styling elements ( 190153b ) Required star not shown on all fields ( 398074c ) Show contact details for all steps on form on referral ( 7522e3a ) Update Jaguar and Land Rover design ( a2f2cd6 ) Volvo ax styling ( a9f2814 ) Wrong button styles for bosch ( f01bb74 ) Features Add admin cutomisable title for widget ( a3b3e1c ) Add audi logo ( f5fe908 ) Add avant styling ( 38bac98 ) Add axicloud data to confirm step on referral forms ( f4d4701 ) Add bentley styles ( 428a5c1 ) Add bmw and vw fonts ( 4daf1bf ) Add bmw styling updates ( f9d7417 ) Add bosch-referral widget theme ( bc1dfe3 ) Add callback time with note input field ( 6a8b82e ) Add clarity to widget fe ( 6bf4b04 ) Add component mappings for bosch client ( 2ca1e96 ) Add conditional path for location input tree ( 5714af5 ) Add confirm steps for vw ( 17d3790 ) Add copy confirmation on contact info copy on referrals ( 55e1e75 ) Add correct bentley icon resources ( a8c2f1f ) Add correct clarity credentials ( 3e346c4 ) Add customisable contact information section ( d8454c3 ) Add default accident assistance theme ( b0a67a7 ) Add dev google analytics measurement id ( f14b524 ) Add dev recaptcha keys ( 15d6902 ) Add google analytics ( c8eb58b ) Add jeep widget assets and styles ( 8abf74b ) Add JLR Accident Assistance styles ( dfb9791 ) Add jlr constrained referral steps ( 4c70b02 ) Add jlr referral client theme and configuration ( c017f5b ) Add jlr theme ( 174db81 ) Add mercedes fonts ( 213caa0 ) Add mini fonts ( 2ce2bc0 ) Add mopar widget style changes and assets ( 7cd1f8b ) Add new repair referral form ( 815775b ) add new samsung design colors matching site ( 18a6019 ) Add option for welcome step ( fdae5a4 ) Add phone icon to contact info on ax man widgets ( b418a42 ) Add pre-commit lint and type check ( 5ba4495 ) add proper vag brand logos ( cd92cf1 ) Add recaptcha verification for non-inured claims ( 8e1c770 ) Add repair location field ( 163dd02 ) Add repair referral form ( 870abf5 ) Add retailer name to agent details ( 6597343 ) Add samsung widget theme ( 0afbec8 ) Add submission key event to analytics ( 5889fef ) Add support for bmw accident assistance theme ( c4c7b38 ) Add support for client theme previews ( 6f30ee4 ) Add support for jaguar and landrover accident assistance clients ( b66aad9 ) Add the aa referral page ( 2d7f9ce ) Add volvo referral page ( b4c4301 ) Add VW styling updates ( ebdcda7 ) Add vwg referral form ( bbcd726 ) Add w3w location to location fields ( 9e4a4ea ) Added audi brand to vag referral steps ( 18ce476 ) Adding automatic user timezone to the submission payload ( 89f072d ) Adding icons to Audi AX client and fine design touches ( ecd9294 ) Adding new design for repair and accident assistance submission steps ( b7deaa2 ) Allow customers to use widget in uninsured contexts ( 1120a1e ) Consolidate referral icons into one place so they are easily reusable for all clients ( fa96d93 ) Create Mercedes styled input fields ( b0f4869 ) Create new Mercedes design ( e1a88b9 ) Display reference only when needed ( d01ba40 ) Fix form title text color ( f84249b ) Hide confirm step banner when submission is errorred ( cdf0978 ) Implement Audi AX client design ( 58cdb22 ) Implement confirm step for samsung theme ( 3d5c0e8 ) Implement optional referral theme ( c6757a4 ) Improve driver selector UI and include stepType into submission payload ( d98b9eb ) improve icon colour and size consistency ( 0d05436 ) Improve input autocomplete behaviour ( b404652 ) Improve statistics data collection ( d852214 ) Improve styles for different client themes, increase developer experience ( 852edaf ) include test mode in the config to support previews ( f11220b ) Make insurance details optional ( d142c57 ) Move business hours to client settings ( aae2970 ) Refine button and text styles for BMW ( 19d506d ) Refine button and text styles for Mini ( f164f1c ) Remove unnecessary client themes and related styles ( 859f989 ) Separate sessions for each submission ( a1cf1b7 ) set user id for clarity ( d84e74c ) Show contact info on second step ( 0e9d102 ) Unify aa and bosch themes into vwg ( 6702288 ) Update accordion styling ( 682bddb ) Update BWM design to new enol variant ( 371b35e ) Update confirm step to support vwg referral ( 7924144 ) Update default ax config ( cd17635 ) Update JLR, BMW and default theming and styles, make the widget more consistent ( 034ffdf ) Update mercedes button design ( 22d7314 ) Update Mini design to new enol variant ( 1df8c65 ) Update missing properties to reload the fields after refresh when session tracking is on ( 6dd585d ) Update radio buttons and checkbox styling ( 0306a63 ) Update recovery required conditions ( 2d48a3e ) Update styling and theming to support new AX Volvo client ( a14fb54 ) 1.12.3 (2024-04-08) Bug Fixes Fix google maps address mapping to correctly match UK style ( 2e6ee4c ) 1.10.0-beta.7 (2024-04-04) Bug Fixes Fix overlay spacing issues ( 647ece2 ) 1.10.0-beta.6 (2024-04-04) Bug Fixes Fix modal height when window height is not appropriate ( d5acfbf ) 1.10.0-beta.5 (2024-03-20) Bug Fixes Map autocomplete issue ( 10cd019 ) 1.10.0-beta.4 (2024-03-20) Bug Fixes Fix missing space on image upload overlays ( a2bf4ff ) 1.10.0-beta.3 (2024-03-20) Bug Fixes Fix map control icons not showing up ( 6e05f4b ) 1.10.0-beta.2 (2024-03-19) Bug Fixes Fix not being able to submit witness overlay on safari if user added address ( 2e06851 ) Fix overlay scrolling and map issues ( 49559ca ) Zoom on input focus on iOS ( 02c57ce ) Features Add type exports ( a3f0a1f ) 1.10.0-beta.1 (2024-03-18) Bug Fixes Adding hover effect to the radio buttons and brake points to title ( a7736d0 ) Call button width on confirm step ( 9a3f3fe ) Driver component validation issues ( 288d95f ) Fix call buttons not working on chrome iOS (made compatible with all browser types) ( 3fb0746 ) Fix driver question sapcing and error display ( 54fdf10 ) Fix inconsistencies of contact (phone and email) buttons throughout app ( 7499fb8 ) fix issue with jwt token initialisation ( c391a3f ) Fix map marker default state on autocomplete not correct ( e52f9fc ) Fix page not scrolling top on submisson ( 51f3f85 ) Fix radio button label spacing ( 6f070a9 ) Fix spacing issues that caused text clipping on submission page ( e3e6291 ) Make arrows black on volvo theme ( 3d21fcb ) Minor style changes across the widget ( 92e887a ) Replace initial step if only one option is available ( a1ef13f ) Resolve empty session data issue and minor design fixes ( 3e27e51 ) Scroll up when user reaches submission page ( dceea0d ) Update line height for title ( bc94923 ) Features Add new text-rednering styling ( 2ddf59b ) Adding icons and different config settings for Mini, Bmw and Mercedes clients ( 4236427 ) Implement BMW styling ( cb5c742 ) Implement Mini Cooper styling ( 377b2b0 ) Minor design changes for Volvo ( 1862030 ) Update confirm dialog styling to match volvo's guide ( fb82419 ) 1.0.0-beta.52 (2024-03-14) Features Add new text-rednering styling ( 2ddf59b ) 1.0.0-beta.51 (2024-03-12) Bug Fixes Replace initial step if only one option is available ( a1ef13f ) Update line height for title ( bc94923 ) 1.0.0-beta.50 (2024-3-5) Bug Fixes Call button width on confirm step ( 9a3f3fe ) 1.0.0-beta.49 (2024-3-4) Bug Fixes Fix call buttons not working on chrome iOS (made compatible with all browser types) ( 3fb0746 ) 1.0.0-beta.48 (2024-3-4) Bug Fixes Fix spacing issues that caused text clipping on submission page ( e3e6291 ) 1.0.0-beta.47 (2024-2-29) Bug Fixes Fix page not scrolling top on submisson ( 51f3f85 ) 1.0.0-beta.46 (2024-2-23) Bug Fixes Adding hover effect to the radio buttons and brake points to title ( a7736d0 ) 1.0.0-beta.45 (2024-2-23) Features Minor design changes for Volvo ( 1862030 ) 1.0.0-beta.44 (2024-2-20) Features Implement BMW styling ( cb5c742 ) Implement Mini Cooper styling ( 377b2b0 ) CHANGELOG V1.2.1 (2023-08-29) Bug Fixes Use primary font only for heading ( 2477b4c ) V1.2.0 (2023-08-29) Bug Fixes Add tab icon ( b44eadb ) Change pixel values to rem values ( df151eb ) changing the schema type to array for all image section (vehicle images, additional images) ( 5d01b61 ) Fixed docs not building because of ssr issues ( fa38457 ) Fixed wrong font urls for customisable fonts ( ae37814 ) Features Add customizable icons (save, delete, edit) and finish land rover styling ( 6a6ad9d ) Add possibility to use load function with encoded options ( b5ff986 ) Added customisable map marker icon ( 5ae4157 ) Added error handling on missingproperties ( 3d82169 ) Added missing property inputs to json schema correctly ( 58b739f ) Create inputs for collecting the missing properties ( be96d45 ) Extended editable properties of json form ( ec97e38 ) Make widget ssr friendlier ( 30f8849 ) V1.1.0 (2023-08-21) Features Replaced dev branch with beta for prerelease version ( a68c680 ) V1.0.0 (2023-08-21) Bug Fixes Remove unnecessary npm publish step ( fdcd873 ) Features Create a more complex address component for overlay address inputs ( f92b212 ) Fixed workflows ( 10ced76 ) License © 2023 Axitech. All rights reserved.",1780929103924]