Build on a Stable,
OpenAPI service
A REST API for feedback. Signed webhooks. An MCP server.
Runtime OpenAPI so your clients always match the deployed service.
OpenAPI you can curl
Specs served from /openapi.yaml and /openapi.json. Point your client generator at the live URLs. No drift.
Signed webhooks, no polling
Subscribe to new or updated records. The worker signs each payload and retries with backoff. Route into Slack, Zendesk, or your warehouse.
- 1
Authenticate
- Description
- One bearer token for the API, webhooks, MCP, and search.
- 2
Send or read
- Description
- POST records against an OpenAPI contract. Read via API or SQL.
- 3
React in real time
- Description
- Subscribe to webhooks. No polling.
What the API exposes
Every integration surface you'd want
OpenAPI at runtime
Specs served from /openapi.yaml and /openapi.json. Client generators always match the deployed service.
Bearer tokens
Standard bearer auth. Tenant isolation on every endpoint.
Signed webhooks
Signed, retried deliveries. No polling, no scheduled exports.
Similar feedback
Pull up records that mean the same as this one, even when worded differently.
MCP for AI clients
Built-in MCP server. Agents read records with the same auth as REST.
Validated schema
Nine typed field types. Bad payloads rejected at the door.
MCP for AI clients
Claude, Cursor, or any MCP client can read records and run search. Same bearer token as REST.
Find similar feedback
Pass a record and Hub returns the ones that mean the same thing. Across surveys, reviews, and support. No keyword matching required.
10,000+ teams at the world's best companies trust Formbricks
A contract you can build on
OpenAPI at runtime, signed webhooks, MCP, and similar feedback. One auth model.
FAQ