> 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 and access to the **API section** of your dashboard. This is where you'll get your credentials and tell us where to send your webhooks.

![The portal Overview — your home for credentials, webhook URLs, delivery stats, and the staging environment.](https://3825213797-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjBgAFiZ99Eug1CmRq2QO%2Fuploads%2Fx9NlITX9PdMkpyhOJnWG%2Fportal-overview.png?alt=media)

## Steps

1. **Create an account.** Sign up for InsurGrid and sign in to your dashboard.
2. **Open the API section.** In the dashboard, go to the **API** area. This is your home for everything in these docs — credentials, webhook URLs, and delivery logs.
3. **Add your webhook URLs.** For each topic you want to receive (for example, `client-submission`), add the URL InsurGrid should `POST` to. You can add a **staging** URL and a **production** URL separately, so you can test without touching live traffic.
4. **Start using them.** Once a URL is saved for a topic, InsurGrid begins delivering matching events to it.

![Registering a webhook endpoint — enter your destination URL, pick the topic, and choose how deliveries are authenticated (Default signs every request).](https://3825213797-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjBgAFiZ99Eug1CmRq2QO%2Fuploads%2FPlw2N8Qp4OnhpVZGdS5j%2Fregister-endpoint.png?alt=media)

## Staging vs production

You'll add URLs for **two environments**:

| Environment    | Use it for                                            | Example URL                                    |
| -------------- | ----------------------------------------------------- | ---------------------------------------------- |
| **Staging**    | Building and testing your integration. Safe to break. | `https://staging.your-app.com/hooks/insurgrid` |
| **Production** | Real customer data, once your integration works.      | `https://your-app.com/hooks/insurgrid`         |

Build and verify everything in **staging** first. When it works end to end, add the production URL and switch over. See [Testing & go-live](/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](/get-started/05-local-development.md). Don't skip this; it's the one step that isn't obvious.

Next: [Get your API credentials →](/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.insurgrid.com/get-started/02-get-access.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.