Data Sharing via URL

Here is a guide to pre-filling authentic application question fields through the URL

Forwarding data to your Authentic application flow is as simple as attaching one search parameter to your redirect URL:

https://[tenant_name].prod.authenticinsurance.com/apply?prefill_data=[payload]

The data parameter should be base64 encoded JSON with the following types in the following format:

{
    lead?: {
      email?: string;
      businessClassCode?: string;
      stateCodes?: string[];
      productIds?: string[];
    }
    responses?: {
      exposures?: Array<{
        exposureName: string;
        fieldValues: Record<string, string>;
      }>;
      questions?: Record<string, string>;
    }
  }

For reference here is a tool to convert between JSON and base64 encoding: https://codebeautify.org/json-to-base64-converter

  {
    lead: {
      email: "[e-mail]",
      stateCodes: ["OH", "WY"],
      businessClassCode: "20831"
    },
    responses: {
      exposures: [{
        exposureName: "business_location",
        fieldValues: {
          "ADDRESS": "100 street, UNIT 2, city, OH 33333, US",
          "SALES": "100000",
          "AREA": "2000"
        }
      }],
      questions: {
        "BUSINESS_LEGAL_NAME": "Authy Insurance Services, Inc.",
        "NAME": "Liam Frank",
        "PHONE": "2014206735",
        "MAILING_ADDRESS": "200 street, UNIT 5, Dayton, OH 33333, US"
      }
    }
  }

Which, encoded would look like this:

ewogICAgbGVhZDogewogICAgICBlbWFpbDogImxmcmFua0BhdXRoZW50aWNpbnMuY29tIiwKICAgICAgc3RhdGVDb2RlczogWyJPSCIsICJXWSJdLAogICAgICBidXNpbmVzc0NsYXNzQ29kZTogIjIwODMxIgogICAgfSwKICAgIHJlc3BvbnNlczogewogICAgICBleHBvc3VyZXM6IFt7CiAgICAgICAgaWQ6ICIxIiwKICAgICAgICBleHBvc3VyZU5hbWU6ICJidXNpbmVzc19sb2NhdGlvbiIsCiAgICAgICAgZmllbGRWYWx1ZXM6IHsKICAgICAgICAgICJBRERSRVNTIjogIjEwMCBzdHJlZXQsIFVOSVQgMiwgY2l0eSwgT0ggMzMzMzMsIFVTIiwKICAgICAgICAgICJTQUxFUyI6ICIxMDAwMDAiLAogICAgICAgICAgIkFSRUEiOiAiMjAwMCIKICAgICAgICB9CiAgICAgIH1dLAogICAgICBxdWVzdGlvbnM6IHsKICAgICAgICAiQlVTSU5FU1NfTEVHQUxfTkFNRSI6ICJBdXRoeSBJbnN1cmFuY2UgU2VydmljZXMsIEluYy4iLAogICAgICAgICJOQU1FIjogIkxpYW0gRnJhbmsiLAogICAgICAgICJQSE9ORSI6ICIyMDE0MjA2NzM1IiwKICAgICAgICAiTUFJTElOR19BRERSRVNTIjogIjIwMCBzdHJlZXQsIFVOSVQgNSwgRGF5dG9uLCBPSCAzMzMzMywgVVMiCiAgICAgIH0KICAgIH0KICB9

would then pass via the pre-fill data parameter as:

https://[tenant_name].prod.authenticinsurance.com/apply?prefill_data=ewogICAgbGVhZDogewogICAgICBlbWFpbDogImxmcmFua0BhdXRoZW50aWNpbnMuY29tIiwKICAgICAgc3RhdGVDb2RlczogWyJPSCIsICJXWSJdLAogICAgICBidXNpbmVzc0NsYXNzQ29kZTogIjIwODMxIgogICAgfSwKICAgIHJlc3BvbnNlczogewogICAgICBleHBvc3VyZXM6IFt7CiAgICAgICAgaWQ6ICIxIiwKICAgICAgICBleHBvc3VyZU5hbWU6ICJidXNpbmVzc19sb2NhdGlvbiIsCiAgICAgICAgZmllbGRWYWx1ZXM6IHsKICAgICAgICAgICJBRERSRVNTIjogIjEwMCBzdHJlZXQsIFVOSVQgMiwgY2l0eSwgT0ggMzMzMzMsIFVTIiwKICAgICAgICAgICJTQUxFUyI6ICIxMDAwMDAiLAogICAgICAgICAgIkFSRUEiOiAiMjAwMCIKICAgICAgICB9CiAgICAgIH1dLAogICAgICBxdWVzdGlvbnM6IHsKICAgICAgICAiQlVTSU5FU1NfTEVHQUxfTkFNRSI6ICJBdXRoeSBJbnN1cmFuY2UgU2VydmljZXMsIEluYy4iLAogICAgICAgICJOQU1FIjogIkxpYW0gRnJhbmsiLAogICAgICAgICJQSE9ORSI6ICIyMDE0MjA2NzM1IiwKICAgICAgICAiTUFJTElOR19BRERSRVNTIjogIjIwMCBzdHJlZXQsIFVOSVQgNSwgRGF5dG9uLCBPSCAzMzMzMywgVVMiCiAgICAgIH0KICAgIH0KICB9

Parameter Naming Conventions for URLs

In our application, URL parameters are standardized to use snake_case (e.g., application_id) or kebab-case (e.g., application-id) rather than camelCase. This convention is followed to ensure consistency and to avoid potential issues with case sensitivity, which can sometimes cause confusion or errors in URL parsing. This practice aligns with common web development standards, similar to how UTM parameters (e.g., utm_source) are formatted. Importantly, this convention is consistent across all production & sandbox environments.