> 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.md).

# Get started

InsurGrid sends your app structured insurance data — extracted policy details and completed intake forms — pushed to a URL you control. This section takes you from zero to your first received webhook in about 30 minutes.

```mermaid
flowchart LR
    A["A customer submits<br/>(dec page or form)"] --> B["InsurGrid processes it"]
    B --> C["We POST to your URL"]
    C --> D["Your server receives it"]
```

## The path

Follow these in order — each page is a few minutes:

1. **What you can build** — the two kinds of data you can receive, and the one envelope they share.
2. **Get access** — create an account and open the API section where credentials and webhook URLs live.
3. **Get your API credentials** — your API token and signing secret, and what each is for.
4. **Set up a webhook endpoint** — stand up an HTTPS URL that returns `2xx`, and register it.
5. **Expose your local endpoint** — the one non-obvious step: give your `localhost` a public HTTPS URL for testing.

## Then pick a quickstart

Once you're set up, follow a runnable, end-to-end guide for your use case:

* [**Receive policy data**](/quickstarts/a-receive-policy-data.md) — get extracted policy fields by webhook (the simplest path — start here).
* [**Embed a form & receive submissions**](/intake-forms/b-embed-form.md) — drop an InsurGrid intake form into your app.
* [**Build forms via the API**](/intake-forms/c-build-forms-api.md) — create and publish forms from your backend.

New to webhooks? Every term is defined inline the first time it appears, and collected in the [Glossary](/glossary.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.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.