> 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/intake-forms.md).
# Intake Forms
Collect a customer's details through an InsurGrid form, and get the answers back as structured data.
An intake form collects what you need from a customer before you can quote them. InsurGrid builds, hosts and runs the form; you get the answers back as structured data — every response, any files they uploaded, and filled ACORD PDFs where the form maps onto them.
An integration has three parts: **build** a form, **share** it, and **receive** what comes back.
***
## 1. Build a form
Two ways, and they work on the same forms — build one in the embedded builder and manage it through the API later, or the other way round.
### Let your users build it — the embeddable builder
Drop InsurGrid's form builder into a page of your own product and your users build and edit their own forms by clicking, without leaving your app.
They don't need InsurGrid accounts, and each signed-in user sees only their own forms. You add a snippet to the page and one route on your server that hands the builder a short-lived token — your API key never reaches the browser.
```html
```
Best when the people building forms aren't developers. Full walkthrough: [Embed the form builder](/intake-forms/builder-sessions.md).
### Build it from your backend — the API
Create a draft with `POST /api/v1/forms`, set its steps and questions with `PATCH`, then publish with `PUT /api/v1/forms/{id}/publish`.
Best for templating, bulk creation, automation, or keeping form definitions in source control. Reference: [Forms API](/intake-forms/forms.md) · walkthrough: [Build forms via the API](/intake-forms/c-build-forms-api.md).
> **Forms built in the InsurGrid dashboard are separate.** The API and the embedded builder both work on forms that belong to one of *your* users. A form an agent creates in the InsurGrid dashboard has no such owner, so it won't appear in `GET /forms` and `GET /forms/{id}` returns `404` for it.
## 2. Share it
A published form has a `shareUrl` — an ordinary web address. Send it to a customer, link to it from your site, or put it in an iframe if you'd rather it appeared inside your own page.
Walkthrough: [Share a form and receive submissions](/intake-forms/b-embed-form.md).
## 3. Receive what comes back
Every completed form appears in your InsurGrid dashboard, with nothing to set up.
To get submissions into your own systems as well, register a webhook endpoint. InsurGrid posts each one to you as a `form-submission` event — every answer, links to any uploaded files, and a link to the filled ACORD PDFs — through the same signed, at-least-once delivery pipeline used for policy data, with a delivery log and replay.
> **Submissions are delivered, not fetched.** The Forms API doesn't return them, so store what you need when the event arrives. See [Submissions](/intake-forms/submissions.md).
***
## In this section
* [Share a form and receive submissions](/intake-forms/b-embed-form.md) — get a published form in front of customers, and the answers back.
* [Build forms via the API](/intake-forms/c-build-forms-api.md) — create, structure and publish forms from your backend.
* [Forms API](/intake-forms/forms.md) — the full endpoint, error and rate-limit reference.
* [Embed the form builder](/intake-forms/builder-sessions.md) — let your users build their own forms inside your product.
* [Submissions](/intake-forms/submissions.md) — how completed forms reach you.
* [Tracking & analytics](/intake-forms/tracking-and-analytics.md) — see which ads produce leads, and how many people finish the form. Set up a Meta Pixel or a Google Tag Manager container in a few clicks; no code needed.
## Related
* [The two embeds](/guides/embeds.md) — the builder versus the form customers fill in.
* [Environments](/guides/environments.md) — staging and production addresses.
---
# 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/intake-forms.md?ask=&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.