> 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/developer-platform.md).

# InsurGrid Developer Platform

Build insurance workflows on InsurGrid. Collect a customer's information once, and InsurGrid sends you structured insurance data — extracted policy details, completed intake forms, and filled ACORD forms — pushed straight to your app.

You don't poll us. You give us a URL you control, and we `POST` the data to it the moment it's ready.

## What you can build

* **Receive policy data** — when a declaration page is submitted and processed, we send you the extracted policy fields (coverages, premiums, named insured, and more) as a webhook.
* **Embed an intake form** — drop an InsurGrid form into your app with one iframe. When someone completes it, we send you the full submission — every answer, links to uploaded files, and the filled ACORD PDFs.
* **Build and manage forms from your backend** — create, update, and publish forms entirely through the API.

> **New term — webhook:** a webhook is just an HTTP `POST` that *we* send to *your* server when something happens, instead of you having to ask us repeatedly.

## Pick your path

| I want to…                              | Start here                             |
| --------------------------------------- | -------------------------------------- |
| Receive policy data from a submission   | Quickstart A — Receive policy data     |
| Embed an intake form in my app          | Quickstart B — Embed a form            |
| Create and manage forms from my backend | Quickstart C — Build forms via the API |

New to InsurGrid? Read **Get started** first — it walks you from account to first webhook in order.


---

# 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/developer-platform.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.