> 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/02-get-access.md).

# Get access

To start receiving data, you need an InsurGrid account with access to the **Webhooks** section of your dashboard. That's where you tell us where to send your webhooks, test them, and watch every delivery. There's no separate portal or second login — you use your normal InsurGrid sign-in.

## Steps

1. **Get an account.** New API customers get a welcome email from InsurGrid — open the link, set your password, and add your name and phone number. Already have a dashboard account? Just sign in. (Full detail: [Access the portal](https://docs.insurgrid.com/data-webhook-page/quickstart.md).)
2. **Open Webhooks.** In the dashboard's left sidebar, open **Webhooks**. It has five pages: **Overview**, **Endpoint**, **Test flow**, **Logs** and **API plans**. See the [Webhooks portal overview](https://docs.insurgrid.com/data-webhook-page/readme.md).
3. **Register your endpoint.** On **Webhooks → Endpoint**, add the HTTPS URL InsurGrid should `POST` to, tick the events you want (`client-submission`, `form-submission`, or both), and choose how deliveries are authenticated. See [Endpoint](https://docs.insurgrid.com/data-webhook-page/destination.md).
4. **Start receiving.** Once the endpoint is saved, InsurGrid delivers matching events to it.

{% hint style="info" %}
Only the agency's **owners and admins** can open the Webhooks pages. If you don't see **Webhooks** in your sidebar, your account doesn't have API access yet — [contact us](https://docs.insurgrid.com/support.md).
{% endhint %}

## Test mode vs Live

A **Test mode / Live** toggle sits at the top right of every Webhooks page. Each mode has **its own endpoint and its own delivery logs**:

| Mode          | Use it for                                                                                                  | Cost                   |
| ------------- | ----------------------------------------------------------------------------------------------------------- | ---------------------- |
| **Test mode** | Building and testing your integration. Only the demo client, *Jimmy Swanson*, flows through. Safe to break. | Free, forever.         |
| **Live**      | Real submissions from your clients, once your integration works.                                            | Needs a paid API plan. |

Build and verify everything in **Test mode** first. When it works end to end, switch to **Live**, choose a plan, and register your production endpoint there. See [Sandbox & testing](https://docs.insurgrid.com/testing/sandbox.md) for the full flow.

> **Developing on your own machine?** Your local server is `http://localhost:3000`, which InsurGrid can't reach. You'll expose it with a public HTTPS URL — see [Expose your local endpoint](https://docs.insurgrid.com/get-started/05-local-development.md). Don't skip this; it's the one step that isn't obvious.

Next: [Get your API credentials →](https://docs.insurgrid.com/get-started/03-api-credentials.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/02-get-access.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.
