canonical: https://jentic.com/apis/feedbucket.app/feedbucket

# Feedbucket App Feedbucket REST API

The Feedbucket REST API manages the website feedback and bug reports your team collects through the Feedbucket widget. It lists, reads, and updates feedback items on a project, threads comments on each one, and returns the browser console log captured alongside a bug so a developer can reproduce it. Projects can be created, updated, and archived with their widget settings, and a presigned upload URL lets you attach screenshots and recordings to a feedback item.

## For AI agents

List and triage website feedback and bug reports across projects, comment on them, and read the console log captured with each bug. Create, update, and archive projects and their feedback widgets.

## Scope

Does not handle session replay, uptime monitoring, or analytics dashboards. Use for collecting and triaging website feedback and bug reports only.

## Capabilities

- Collect and list website feedback and bug reports as feedback items on a project
- Filter feedback and update an item, including its status and resolution
- Read the browser console log captured with a bug report to reproduce it
- Add and edit comments on a feedback item to discuss it with your team
- Create, update, and archive projects, each with its own feedback widget settings
- Mint a presigned upload URL to attach screenshots and recordings to feedback

## Use cases

### Agent triage of website feedback through Jentic

An AI agent polls a project for new feedback, reads each item with its captured console log, sets a status, and leaves a comment summarising the likely cause. Because every item carries the widget-captured context, the agent can route a reproducible bug to engineering and a vague note back to the reporter without a person opening the dashboard first.

Example prompt: List open feedback for a project, read the console log on the newest bug, and update that item's status to resolved with a comment

### Sync feedback into an engineering workflow

Teams want website feedback to become tracked work. The API lists feedback per project and exposes each item's details and comments, so a connector can mirror new bugs into an issue tracker and write the issue link back as a comment, keeping the reporter and the developer on the same thread.

Example prompt: Fetch feedback created since yesterday for a project and add a comment on each one linking the mirrored issue

### Reproduce bugs from captured console logs

A website bug report is only useful if a developer can reproduce it. Feedbucket captures the browser console log with the feedback, and the API serves that log on demand, so a debugging assistant can pull the errors, correlate them with the described steps, and attach its findings as a comment before a human picks it up.

Example prompt: Retrieve the console log for a specific feedback item and summarise the errors it contains in a new comment

### Project and widget setup automation

Agencies onboard new client sites repeatedly. The API creates a project, updates its widget settings such as visibility and enabled features, and archives it when the engagement ends, so onboarding and offboarding a site becomes a scripted step instead of manual dashboard work.

Example prompt: Create a project for a new client site, set its visibility to members only, then archive a completed project

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/projects` | List projects |
| POST | `/projects` | Create a project |
| GET | `/projects/{project}/feedback` | List feedback for a project |
| GET | `/projects/{project}/feedback/{feedback}` | Get a feedback item |
| PATCH | `/projects/{project}/feedback/{feedback}` | Update a feedback item |
| GET | `/projects/{project}/feedback/{feedback}/console-log` | Get the console log captured with a bug |
| POST | `/projects/{project}/feedback/{feedback}/comments` | Add a comment to a feedback item |
| POST | `/attachments` | Mint a presigned upload URL for an attachment |

## Key resources

- **Projects** — Create, read, update, archive, and restore projects and their feedback widget settings
- **Feedback** — List, read, and update website feedback and bug reports, including the captured console log
- **Comments** — Add, update, and delete comments threaded on a feedback item
- **Attachments** — Mint a presigned upload URL for screenshots and recordings

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 45 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 64 / 100
  - AI-Readiness & Agent Experience: 20 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/feedbucket.app/feedbucket/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Feedbucket by hand means creating a personal access token with the api:use scope, sending it as a Bearer token, and handling its team-scoped requests and rate limiting yourself. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Feedbucket puts the project id in the URL path (`/projects/{project}/...`), so a rule can pin your agent to one project: it reads and triages that project's feedback and nothing else. You choose the operations it may call, so project deletion stays out unless you add it.
- **Credential handling:** Your Feedbucket access token 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 'list website feedback' or 'add a comment to a bug', and Jentic returns the matching Feedbucket operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Canny** — Canny collects product feedback and feature requests on public boards, while Feedbucket captures visual website feedback and bugs.
- **Linear** — Linear tracks engineering issues that Feedbucket website feedback can be turned into.
- **ClickUp** — ClickUp manages tasks and projects that website feedback can feed into as work items.

## FAQ

### What authentication does the Feedbucket REST API use?

It authenticates every request with a personal access token sent as a Bearer token in the Authorization header, per its OpenAPI spec. The token must carry the api:use scope, and requests run as that user within their current team.

### Can I read the browser console log from a bug report with the Feedbucket API?

Yes. Each bug captured through the widget stores the browser console log, and the API serves it for a given feedback item so a developer or an agent can see the errors that fired when the report was filed. It is read-only and sits alongside the feedback item's details and comments.

### What are the rate limits for the Feedbucket REST API?

Feedbucket limits the API to 60 requests per minute per user, as stated in its API documentation. Plan larger feedback syncs around that ceiling and watch for a 429 response when you approach it.

### Is there a Feedbucket MCP server?

Yes, Feedbucket offers an official MCP server. You can also connect Feedbucket directly through Jentic: your agent gets the full 15-endpoint surface without loading another server's tool definitions into its context, your token is injected at call time by your self-hosted instance instead of living in an MCP config, and your rules decide which operations the agent may call.

### Can I limit what my agent is allowed to do with the Feedbucket API?

Yes. Write a rule that allows the feedback-list, feedback-read, and comment operations under one project id, so the agent can triage and reply to feedback for that site while project creation and deletion stay off the list. Every call it makes is recorded in your Jentic One audit log.

### How do I triage website feedback with the Feedbucket API through Jentic?

Search Jentic for 'list website feedback', add the Feedbucket API from the directory, and store your access token once; your agent then lists a project's feedback, reads the console log on each bug, and updates statuses and comments. To run it on your own infrastructure, install Jentic One from its GitHub repo.