Overview
Capture, API, webhooks, and MCP — how FeedByte talks to your product.
FeedByte is a multi-tenant feedback platform. Organizations collect responses at Locations and Stations through surveys, QR codes, and embeds.
This portal is for engineers who need to put capture in a journey, read results from a backend, and react when something happens.
Four surfaces
- Capture — put a survey in a journey (link, QR, embed, or SDK).
- API / SDK — read and write from your backend.
- Webhooks — get pushed when a response, alert, or redemption lands.
- MCP — let an AI assistant query survey analytics.
Base URLs
| Surface | Production |
|---|---|
| API | https://api.feedbyte.io |
| Dashboard | https://feedbyte.io |
| MCP | https://mcp.feedbyte.io/mcp |
| This portal | https://developer.feedbyte.io |
Use the Server SDK or call https://api.feedbyte.io over HTTPS with a secret API key.
Choose a path
Web embed
Drop an iframe or the Capture SDK on a page. Pass station and embed=1.
Call center / CRM
Create a unique /l/{id} with metadata, then read it back on the response.
Mobile banking
Open a survey from the Capture SDK, or deep-link to /s/{id}.
CRM / backend
Register an App, verify signatures, handle response.submitted and alert.triggered.
AI assistant
Connect Cursor, Claude, or any MCP client with the survey:analytics:read scope.
Start with the quickstart if you want a key, a list of surveys, and a verified webhook in one sitting.