canonical: https://jentic.com/apis/featurebase.com/featurebase

# Featurebase API

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.

## For AI agents

Read new feedback posts, create posts, change post status, and fetch changelogs from a Featurebase workspace.

## Scope

Does not handle voting analytics, board configuration, or user provisioning - use for Featurebase post creation, status updates, and changelog reads only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Use Jentic to search 'create a featurebase post' and execute POST `/zapier/create_post` with the consolidated feedback summary and reporter email.

## Key endpoints

| 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 |

## Key resources

- **Authentication** — Identify the current Featurebase user via `/zapier/me`
- **Posts** — Read new posts, create posts, and change post status
- **Comments** — Pull newly added comments for incremental sync
- **Categories** — Detect new categories created on the workspace
- **Changelogs** — Retrieve published changelog entries

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Canny** — Established feedback and roadmap tool with deeper integrations catalogue
- **Savio** — Feedback aggregation focused on customer-account context
- **Aha!** — Strategic roadmap planning that pairs with Featurebase's customer-facing feedback intake

## FAQ

### 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.