> For the complete documentation index, see [llms.txt](https://docs.insurgrid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.insurgrid.com/data-webhook-page/webhooks/data-format/auto/overview.md).

# Overview

## Auto Insurance Webhook

This webhook delivers **auto insurance policy data** when new declaration page is uploaded.\
It provides details about the policy, insured drivers, covered vehicles, coverages, discounts, billing, and insurer contact information.

***

### 🔑 Key Sections in the Payload

#### Document Link

Includes a secure link to the client-uploaded document. The link expires within one hour in accordance with security requirements.

#### Policy Information

* Provider and policy number
* Policy type, term, and effective dates
* Premium and billing details
* Change history (e.g., premium adjustments)

#### Drivers

* Policyholder and listed drivers
* Date of birth and relationship to policyholder

#### Vehicles

* Vehicle details (make, model, year, VIN)
* Usage and location
* Coverage types, limits, premiums, and deductibles

#### Discounts

* Safe driver, multi-policy, early quote, etc.

#### Endorsements

* Special provisions, liability, medical payments, uninsured motorist coverage, etc.

#### Policyholder

* Name and contact details
* Address
* Rating information (e.g., accident-free years)

#### Insurer Information

* Company name and contact numbers
* Agent details (if available)
* Claims and service phone numbers

***

### 📦 Example Payload

```json
{
  "topic": "client-submission",
  "data": {
    "document_link": "https://s3.us-east-2.amazonaws.com/xxxx",
    "policy": {
      "provider": "TRAVELERS PROPERTY CASUALTY INSURANCE COMPANY",
      "policy_number": "607695134 203 1",
      "policy_type": "Auto",
      "policy_term": "12 months",
      "coverage_period": {
        "start_date": "2021-10-16",
        "end_date": "2022-10-16"
      },
      "annual_policy_premium": 1007
    },
    "drivers": [
      {
        "name": "CECILY",
        "date_of_birth": "1958-06-12",
        "relationship_to_policyholder": "Self"
      }
    ],
    "vehicles": [
      {
        "vin": "YV4952DL2E2549538",
        "make": "VOLVO",
        "year": 2014,
        "model": "XC60 3.2",
        "usage": "Pleasure",
        "coverages": [
          {
            "type": "Bodily Injury",
            "limits": "250000/500000",
            "premium": 471,
            "deductible": 0
          }
        ]
      }
    ],
    "discounts": [
      {
        "type": "Safe Driver Discount",
        "description": "5 Years Accident and Violation Free"
      }
    ],
    "policyholder": {
      "name": "CECILY SAPP CARTER SAPP",
      "address": {
        "street": "4286 CABRETTA DR SE",
        "city": "SMYRNA",
        "state": "GA",
        "zip": "30080-6479"
      }
    },
    "insurer_information": {
      "company_name": "TRAVELERS PROPERTY CASUALTY INSURANCE COMPANY",
      "claims_phone": "1.800.252.4633",
      "service_phone": "1.800.842.5075"
    }
  }
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.insurgrid.com/data-webhook-page/webhooks/data-format/auto/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.