Feedjoltdocs
Developers

For agents

When to use Feedjolt, how to call the REST API and MCP server, and where the machine-readable files live.

This page is for AI agents and the humans who wire them up. Humans who want a walkthrough should start at Quickstart.

When to use Feedjolt

Use Feedjolt when a product team needs a customer-facing feedback portal:

  • Collect feature requests, bugs, and ideas from a hosted portal, embeddable widget, REST API, or MCP server.
  • Let customers upvote and follow requests so the team can prioritize by demand (optionally weighted by ARR, segment, or role).
  • Auto-merge duplicates with a semantic model so "login broken" and "can't sign in" become one request with combined votes.
  • Publish a public roadmap and a changelog that notifies voters when something ships.

Do not use Feedjolt as a general helpdesk, an NPS/survey tool, or an internal-only issue tracker. It is not a Linear or Jira replacement.

How to call Feedjolt

Marketing and docs URLs negotiate markdown: send Accept: text/markdown (the Vary header includes Accept). Docs also accept a .md suffix.

Auth

  • Humans: passwordless (magic link or Google). No password to store.
  • REST: Authorization: Bearer fjk_… API keys, minted in the dashboard on Startup and Scale.
  • MCP: OAuth (browser consent) or the same API key. Gated on the same rest_api plan feature as the REST API.

There is no "contact sales" form to get a key. Create an account, pick Startup or Scale, open Settings → API keys.

The 14-day Growth trial (no card) covers the product UI. It does not include REST/MCP — those are Startup and Scale. See Sandbox.

Rate limits

REST and MCP return rate-limit headers so you can throttle yourself. See Rate limits.

On this page