REST API
Everything you can do on the board or in the admin area is also an /api/v1 endpoint, with the same permissions as the person calling it. It stays compatible with Fider's API.
Authentication
- API keys (collaborators and administrators): generate one in your user settings and send it as a bearer token. Administrators can add
X-Fider-UserIDto act as a member or collaborator (never as another administrator). - MCP clients (anyone the admin allows, when MCP is on) do not use these endpoints directly: they connect to
/mcp, where every tool maps to one of the endpoints below. See MCP.
curl https://feedback.example.com/api/v1/posts \
-H "Authorization: Bearer YOUR_API_KEY"
Endpoints
The tier is the lowest role that may call it; the route enforces it.
| Area | Endpoints | Tier |
|---|---|---|
| Site | GET /tenant | public |
| Ideas | GET /posts, GET /posts/:number, GET /similarposts, POST /posts, PUT /posts/:number, POST /posts/:number/privacy | public reads, member writes |
| Votes, follows | GET|POST|DELETE /posts/:number/votes, POST /posts/:number/votes/toggle, POST|DELETE /posts/:number/subscription | member |
| Comments | GET|POST /posts/:number/comments, GET|PUT|DELETE /posts/:number/comments/:id, POST /posts/:number/comments/:id/reactions/:reaction | member |
| Vora | GET /ai/ideation-context, POST /ai/ideate, POST /ai/finalize, GET /posts/:number/brief | member |
| You | GET|POST /user/settings, POST /user/change-email, GET /notifications, POST /notifications/read-all | member |
| Team | PUT /posts/:number/status, PUT /posts/:number/product, GET|PUT /posts/:number/internal-note, tags, scorecards and scorecard fields and settings, GET /users, invitations | collaborator |
| Admin | settings (general, theme, advanced, privacy, email sign-in, banner, AI, MCP), products, statuses, webhooks, sign-in providers, roles, block and trust, tag import, system status and update, MCP clients, DELETE /posts/:number | administrator |
Settings endpoints take the whole settings object: read it, change what you need, send it back. Changing your email over the API starts the change; it completes when the emailed link is opened in a signed-in browser.
Private ideas are enforced server-side: nobody receives an idea they may not see from any endpoint, and asking for one by number returns 404.
Webhooks
Configure webhooks in the admin area to receive idea and comment events for your own integrations.
Upvora is open source under AGPL-3.0: a friendly fork of Fider, not affiliated with it.
ยท Built & maintained by