Webhook integration

Outbound webhook delivery is not shipped yet. You can store a webhook URL on a project via the API, but Insito does not currently POST responses to it — only the Slack integration delivers response notifications today. HMAC signing, retries, and event types described as “planned” below are not yet implemented. If you need outbound webhooks, let us know so we can prioritise.

Storing a webhook endpoint

The project integrations API accepts a webhook row containing a URL:

POST /v1/dashboard/projects/:projectId/integrations
Authorization: Bearer <supabase-jwt>
Content-Type: application/json

{ "type": "webhook", "url": "https://api.your-domain.com/webhooks/insito" }

List and remove it via GET /v1/dashboard/projects/:projectId/integrations and DELETE /v1/dashboard/projects/:projectId/integrations/webhook.

Planned payload

When delivery ships, each completed response will trigger a POST to your URL with a payload along these lines:

{
  "type": "response.created",
  "projectId": "uuid",
  "surveyId": "uuid",
  "responseId": "uuid",
  "createdAt": "2026-05-21T18:41:00Z",
  "respondent": {
    "userId": "your-user-id",
    "platform": "ios",
    "appVersion": "2.7.0"
  },
  "answers": [
    { "questionId": "uuid", "type": "nps", "value": 9 },
    { "questionId": "uuid", "type": "open_text", "value": "Love it!" }
  ]
}

Signature verification, retry semantics, and delivery history will be documented here once the feature is available. Until then, use the Slack integration or poll the responses API.

BillingManage your plan, see usage, and update payment methods.

Get started

Concepts

React Native SDK

Flutter SDK

Dashboard

MCP server

Webhook integration

Storing a webhook endpoint

Planned payload

​Storing a webhook endpoint

​Planned payload

Storing a webhook endpoint

Planned payload