Glossary
What this is: every term in these docs is defined inline the first time it's used (look for a "New term" callout). This page is a quick backstop when you land on a page mid-way and need a definition without hunting for where it was first introduced.
Webhook
An HTTP POST that InsurGrid sends to a URL you control when something happens — you don't ask us for the data, we push it to you.
Endpoint
The URL on your server that receives a webhook POST.
2xx
Any HTTP status code from 200 to 299 (e.g. 200 OK). To InsurGrid it means "received, thanks" — anything else, or a timeout, means delivery failed and gets retried.
HMAC signature
A fingerprint of a webhook's raw body, computed with a shared secret. Because only you and InsurGrid know the secret, a matching fingerprint proves the request is genuine and unaltered. Sent in the x-signature header, computed as HMAC-SHA256.
Signing secret
The secret used to compute and verify the HMAC signature on webhooks. Shown once when generated; stays on your server, never sent to InsurGrid.
Bearer token
A secret string sent as Authorization: Bearer <token> that authenticates an API call — whoever holds it can call the API as you.
Management token
The specific bearer token used for Forms API calls (creating, reading, and publishing forms and reading submissions) — issued server-to-server by InsurGrid.
Idempotency key
A value you generate (Idempotency-Key header) and send on a write request, so retrying the exact same request with the same key never performs the operation twice.
Cursor
An opaque value returned by a list endpoint (next_cursor) that you pass back to fetch the next page. Don't construct or parse it yourself.
At-least-once delivery
InsurGrid's delivery guarantee for webhooks: an event will be delivered, but may occasionally be delivered more than once. Your handler must be safe to run twice on the same event.
Topic
The kind of event a webhook carries — client-submission for extracted policy data, form-submission for a completed intake form. You register a URL per topic.
Agency vs. agent
A form (and its submissions) is owned either by an agency (shared across everyone in it) or by a specific agent within that agency. Every form's public fill link is per agent, regardless of ownership scope — that's who a submission gets attributed to.
ACORD
The standardized insurance industry forms (e.g. ACORD 125, 140) that InsurGrid can auto-fill from a completed intake form and return to you as PDFs.