Featurebase API
Agent-ready OpenAPI document · curated by JenticProductivityCollaborationapiKey7 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Read new feedback posts, create posts, change post status, and fetch changelogs from a Featurebase workspace.
Use for: I need to create a Featurebase post from a Slack message, List new feature requests posted since yesterday, Change the status of a Featurebase post to 'in progress', Get the latest published changelogs for our product
Not supported: Does not handle voting analytics, board configuration, or user provisioning - use for Featurebase post creation, status updates, and changelog reads only.
Jentic publishes the only available OpenAPI specification for Featurebase API, keeping it validated and agent-ready. Featurebase is a feedback, roadmap, and changelog tool used by SaaS teams to collect feature requests and broadcast releases. This Zapier-style API exposes the operations needed to read new posts and comments, create posts on behalf of users, change a post's status, and pull changelog entries - enough surface to mirror Featurebase activity into another system or post user feedback from upstream channels.
Install Jentic One Beta
Connect the Featurebase API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Featurebase API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffeaturebase.com%2Ffeaturebase" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffeaturebase.com%2Ffeaturebase" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Featurebase API.
Identify the authenticated Featurebase user via /zapier/me
Pull new posts created since the last poll
Pull new comments and category creations for incremental sync
Create posts on behalf of an end user with /zapier/create_post
Move a post through workflow states with /zapier/change_post_status
Retrieve published changelog entries for release notifications
Use Cases
Patterns agents use Featurebase API for, with concrete tasks.
★ Feedback Capture from Support Tickets
Customer support teams pipe escalated feature requests from Zendesk or Intercom into Featurebase by calling POST /zapier/create_post with the user's email and request text. Featurebase deduplicates, scores, and exposes the request on the public roadmap so PMs can prioritise without leaving the feedback tool.
When a Zendesk ticket is tagged 'feature-request', call POST /zapier/create_post with the ticket title, body, and requester email.
Roadmap Status Sync
Engineering teams keep Featurebase status fields aligned with their issue tracker. A scheduled job calls GET /zapier/new_posts to detect new feedback and POST /zapier/change_post_status to flip a post to 'in progress' when the linked Jira ticket starts, so external customers see real-time progress on the public roadmap.
List new posts via GET /zapier/new_posts, match each to a Jira issue, and call POST /zapier/change_post_status with the matching status.
Agent-Powered Feedback Triage
An AI agent reading customer conversations across Slack, Intercom, and email can use Jentic to discover Featurebase's create_post and change_post_status operations, file structured feedback on the customer's behalf, and update statuses as engineering ships fixes - with the Featurebase API key staying inside your Jentic One instance.
Use Jentic to search 'create a featurebase post' and execute POST /zapier/create_post with the consolidated feedback summary and reporter email.
Key Endpoints
7 endpoints — jentic publishes the only available openapi specification for featurebase api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/zapier/create_post
Create a new feedback post
POST
/zapier/change_post_status
Change status of a post
GET
/zapier/new_posts
List newly created posts
GET
/zapier/new_comment
List newly created comments
GET
/zapier/get_changelogs
Retrieve published changelogs
GET
/zapier/me
Get current authenticated user
POST
/zapier/create_post
Create a new feedback post
POST
/zapier/change_post_status
Change status of a post
GET
/zapier/new_posts
List newly created posts
GET
/zapier/new_comment
List newly created comments
GET
/zapier/get_changelogs
Retrieve published changelogs
GET
/zapier/me
Get current authenticated user
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Featurebase API by hand means setting the X-API-Key header and mapping intent onto its Zapier-style create-post and status-change endpoints yourself. Through Jentic you install once, import Featurebase from the API Directory, store the key once, and your agent calls it.
Permission scoping
Featurebase takes the post and status target in the request body rather than the URL path, so limit the agent to the operations it needs, such as creating a post or reading new comments. You choose which operations it may call, so a write like changing a post status is included only when you add it.
Credential isolation
Your Featurebase X-API-Key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a Featurebase post', and Jentic returns the matching Zapier-style endpoint with its input schema so the agent calls the right endpoint without browsing the docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Featurebase API through Jentic.
Why is there no official OpenAPI spec for Featurebase API?
Featurebase does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Featurebase API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Featurebase API use?
Featurebase uses an API key passed in the X-API-Key header. Through Jentic the raw key is held in the vault and Jentic injects the header at call time so the agent never sees it.
Can I create posts on behalf of users with the Featurebase API?
Yes. POST /zapier/create_post accepts a title, body, and submitter email so a backend or agent can file feedback on behalf of an end user.
What are the rate limits for the Featurebase API?
Featurebase does not document numeric rate limits in this Zapier-style spec. Apply backoff on 429 responses and avoid tight polling loops on /zapier/new_posts.
How do I change a post's status with Featurebase through Jentic?
Run pip install jentic, search 'change featurebase post status', load POST /zapier/change_post_status, and execute it with the post ID and target status.
Does the Featurebase API support pulling changelog entries?
Yes. GET /zapier/get_changelogs returns published changelog entries that can be reposted to release-notes channels or fed into a customer email.
Can I limit what my agent is allowed to do with the Featurebase API?
Yes. Because you run Jentic One yourself, your own rules decide which Featurebase operations and credentials the agent may use. You can allow it to only read new posts, comments, and changelogs via GET /zapier/new_posts, /zapier/new_comment, and /zapier/get_changelogs, and grant write operations like POST /zapier/create_post or POST /zapier/change_post_status only when you add them. Since Featurebase takes the post and status target in the request body rather than the URL path, scoping happens at the operation level you control.
GET STARTED