> 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/get-started/01-what-you-can-build.md).

# What you can build

InsurGrid turns insurance documents and intake forms into structured data, and delivers that data to your application automatically.

Here's the whole idea in one picture:

```mermaid
flowchart LR
    A["1 · A customer submits<br/>(declaration page or<br/>an embedded form)"] --> B["2 · InsurGrid processes it<br/>(extracts / assembles<br/>the structured data)"]
    B --> C["3 · We POST the data<br/>to a URL you gave us"]
    C --> D["Your server<br/>receives it"]
```

You never poll InsurGrid asking "is it done yet?" — you give us a URL, and we send the data to it when it's ready. That's the core of every integration on this platform.

## The two ways data reaches you

**1. Policy data (from a submitted declaration page).** When a declaration page is submitted and processed, we send you the extracted policy — coverages, premiums, the named insured, vehicles or property, and so on — as a webhook.

**2. Form submissions (from an embedded intake form).** When you embed an InsurGrid form and a customer completes it, we send you the full submission: every answer, links to any files they uploaded, and — if the form maps to ACORD forms — a link to the filled ACORD PDFs.

Both arrive the same way: an HTTP `POST` to your endpoint with a small JSON envelope:

```json
{
  "topic": "client-submission",
  "data": { }
}
```

* `topic` tells you *what kind* of event this is.
* `data` holds the actual content. Its shape depends on the topic — the [API reference](/api-reference/webhook-events.md) documents every field.

## What you'll need

Before you write any code, you'll set up three things (the next pages walk through each):

1. An **account** and access to the **API section**.
2. Your **API credentials** — a token and a signing secret.
3. A **webhook endpoint** — an HTTPS URL on your server that can receive a `POST`.

That's it. If you can run a small web server and make an HTTPS URL reachable, you can complete a quickstart in under 30 minutes.

Next: [Get access →](/get-started/02-get-access.md)


---

# 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/get-started/01-what-you-can-build.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.