> 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/changelog.md). # Changelog **What this is:** a dated record of changes to these docs and to the underlying API/webhook behavior they document. Each entry is dated so you can tell whether something you're relying on has changed since you last read a page — check here if behavior seems different from what you remember, or from what a saved copy of a page says. *** ## 2025-10-13 — Developer portal rebuilt The InsurGrid webhook and declaration-page documentation has been rebuilt and reorganized. * **Reorganized around your task**: [Get started](/get-started/01-what-you-can-build.md) → [Quickstarts](/quickstarts/a-receive-policy-data.md) → [Guides](/guides/authentication.md) → API reference → [Testing & go-live](/testing/sandbox.md). * **Policy data and form submissions are now documented as two distinct webhook events** (`client-submission` and `form-submission`), each with its own payload reference, instead of being mixed together. * **Added a full sandbox flow**: staging URLs and credentials, a send-a-test-event action, and a delivery log with replay — see [Sandbox & testing](/testing/sandbox.md). * **The existing REST-API and Zapier pages are unchanged** and remain where they were. See [Migrating from the previous docs](/testing/migrating.md) for the moved-page mapping. ## Related * [Migrating from the previous docs](/testing/migrating.md) * [Support & contact](/support.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/changelog.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.