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

# Support & contact

**What this is for:** these docs are written so a working integration doesn't require asking anyone anything. But when you genuinely get stuck — an undocumented edge case, something that looks like a bug, a question about your account — here's the escape hatch.

## Before you reach out

Two pages solve most problems faster than a support ticket:

* [Troubleshooting: my webhook isn't arriving](/testing/troubleshooting.md) — the ordered checklist for the most common failure.
* [Integration checklist](/testing/integration-checklist.md) — a final pass that catches the usual gaps (signature over raw bytes, de-dupe, expiring file links).

## Contact InsurGrid

Email [**support@insurgrid.com**](mailto:support@insurgrid.com) with your question. Include a `request_id` or `trace_id` and a rough timestamp (see below) so we can find the exact request or event fast.

## Quote your request\_id or trace\_id

Every error response carries a `request_id`. Every submission and webhook delivery carries a `trace_id`. Both are correlation identifiers InsurGrid support can use to pull up the exact request or event you're asking about — without one, diagnosing an issue takes much longer, and sometimes isn't possible at all.

> **New term — correlation id:** a unique value attached to one specific request or event, so it can be looked up later without ambiguity. `request_id` identifies one API call; `trace_id` identifies one submission or webhook delivery.

Before contacting support:

1. Find the relevant `request_id` (in an error response body) or `trace_id` (in a submission or webhook payload, or the delivery log).
2. Include it verbatim in your message, along with the topic/endpoint and roughly when it happened.
3. If it's a webhook delivery issue, also check the **delivery log** in the API section first — it often already shows what went wrong.

A support request with a `request_id` or `trace_id` and a rough timestamp is almost always resolved faster than one without.

## Related

* [Troubleshooting: my webhook isn't arriving](/testing/troubleshooting.md)
* [Sandbox & testing](/testing/sandbox.md)
* [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/support.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.