Featurebase API
What the Featurebase API is, what you can build with it, and the basics: authentication, versions, pagination and errors.
Written By Robi Rohumaa
Last updated About 1 hour ago
The Featurebase API lets you read and write the data in your Featurebase workspace from your own code: feedback, roadmaps, changelogs, help center articles, conversations, tickets, contacts and companies, reports and more. Use it to sync customer data, collect feedback from your own forms and tools, publish content from your release pipeline, or build internal tools and AI agents on top of Featurebase.
👨💻 New to the API? Start with Getting started with the Featurebase API. It takes you from an API key to your first request in about five minutes.
What you can build
Sync customer data. Create or update contacts and companies, so every request, conversation and vote is tied to the right customer, plan and revenue.
Collect feedback anywhere. Send feedback from your own forms, product, CRM or call recordings and turn it into requests.
Publish product updates. Create, update and publish changelog entries from your release process.
Manage your help center. Create and edit articles and collections, and keep your API reference in sync from CI.
Work with support data. Read and act on conversations and tickets, manage tags and attributes, and query reports.
Train your AI agent. Push training files and Q&A entries from your own systems.
React in real time. Subscribe to webhooks to get an HTTP callback when something happens in your workspace.
The basics
Versioning
Each API version is named by its release date, for example 2026-08-19.orbit. Newer versions can add fields to responses at any time; removed or renamed fields and changed behaviour only ever ship in a new version. Pin the version you build against, and your integration keeps working until you choose to upgrade.
Use the API with AI agents (MCP)
Connect Claude, ChatGPT, Cursor or any MCP client to https://mcp.featurebase.app. You sign in with your Featurebase account, and the agent gets typed tools for the same API, limited by your access. Reads need the mcp:read scope and changes need mcp:write. Some sensitive actions, such as publishing or deleting an API spec, are only available with an API key.
Next steps
Getting started with the Featurebase API: your first requests, step by step.
Collecting feedback through the API: choose the right intake mode for your forms and integrations.
Creating and signing a JWT: sign your users in to the portal, widgets and Messenger.
Browse the endpoints in the sidebar. Every endpoint page lists its parameters and response fields, with examples you can try.