Feedback1
Feedback1feedback1.ai

AI-assisted Feedback Management for SaaS

Webhooks

Subscribe a URL to Feedback1 events so your own tools can react when feedback, features, or changelog records change.

What you can do

  • Create a webhook with a name, destination URL, and event list
  • Scope events to one or more products, or receive all products
  • Store the signing secret from the create response (it is shown once)
  • Send a test ping, inspect deliveries, and rotate the secret

How to

  1. Open app.feedback1.ai → Settings → API Keys and create a key with the access you need.
  2. List the event types your workspace supports with GET https://app.feedback1.ai/api/v1/webhooks/events and a Bearer token.
  3. Create the webhook with POST https://app.feedback1.ai/api/v1/webhooks. Send JSON with name, url, and events. Add product_ids when you want a product filter.
  4. Save the secret from the create response. Use it to verify signatures on incoming posts.
  5. Call POST /api/v1/webhooks/{webhook_id}/test to send a test.ping event, then confirm your URL received it.
  6. Review deliveries with GET /api/v1/webhooks/{webhook_id}/deliveries. Rotate the secret from POST /api/v1/webhooks/{webhook_id}/rotate-secret if it leaks.

Example create request:

curl -sS https://app.feedback1.ai/api/v1/webhooks \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"My listener","url":"https://example.com/hooks/feedback1","events":["test.ping"]}'

Limits

  • The create response is the only time the full secret is returned. Store it before you close the response.
  • Rotating the secret immediately invalidates the old one.
  • Webhooks are a Public API feature. Manage them with your API key, not from a Coming soon integration card.
  • Follow the live OpenAPI event list. Do not subscribe to names you did not see in GET /webhooks/events.

Related

PreviousMCP IntegrationNext Public API
Feedback1