Developers
Integrate Feedjolt into your app with the embeddable widget, signed webhooks, and the REST API. Quickstart, references, and the bug-reporting workflow.
This section is for engineers. If you're configuring Feedjolt as an admin (turning Slack on, inviting members), the Integrations section is friendlier. If you're writing code that talks to Feedjolt, you're in the right place.
What you can build
- Embed feedback inside your app - drop in the widget.
- React to events - webhooks deliver signed JSON to your endpoint when feedback moves.
- Read and write programmatically - the REST API covers most of what the dashboard does.
Where to start
- Quickstart - a 10-minute integration: widget on your site, an API key in your hand, a webhook hitting your dev server.
- For agents - when to use Feedjolt, OpenAPI, MCP, markdown.
- Widget - installation, configuration, customization, CSP.
- Webhooks - payload reference, signature verification, retry behavior.
- API - authentication, rate limits, errors, pagination, links to the full OpenAPI reference.
- MCP - Streamable HTTP server for Claude, Cursor, and other agents.
- Sandbox - self-serve signup, trial, and API keys.
API reference
The interactive endpoint reference is at https://api.feedjolt.com/docs (Swagger UI, with try-it). OpenAPI JSON: https://www.feedjolt.com/openapi.json (also at https://api.feedjolt.com/openapi.json). YAML: https://www.feedjolt.com/api/openapi.yaml. MCP server card: https://www.feedjolt.com/.well-known/mcp.json.
The pages in this section cover cross-cutting behavior (auth, errors, pagination, webhook contract) - the OpenAPI ref is canonical for per-endpoint shape.
What's coming
A few things on the roadmap we know developers ask for:
- Automatic webhook retries with exponential backoff.
- Signed-timestamp webhook signatures (Stripe-style replay protection).
- A
window.feedjolt.open()JS API for custom widget triggers. - Official TypeScript and Python SDKs.
Vote on what would unblock you.
Reporting bugs
If something behaves weirdly:
- Reproduce in a fresh dev workspace so we can see the same data.
- File at /en/contact with the request ID from
X-Request-ID(every API response carries one). - For widget bugs, paste your install snippet and any CSP errors from the console.
Public API
Feedjolt's REST API uses JSON and Bearer-token auth. Read and write posts, comments, votes, statuses, and more. Full interactive reference at api.feedjolt.com/docs.
Quickstart
Install the Feedjolt widget, create an API key, and receive your first webhook on a local tunnel. A 10-minute developer quickstart - skip what you don't need.