Build agent workflows on FeedbackBasket.
Use the FeedbackBasket REST API, MCP server, CLI, agent skill, and signed webhooks to collect and operate on product feedback. These interfaces let an agent resolve the correct project, inspect feedback and bugs, search customer reports, update triage state, add notes, export context, and react to new feedback without scraping the dashboard.
Agent surface version 3.1.0 gives the CLI, stdio MCP package, and live Streamable HTTP server the same 31 product operations.
FeedbackBasket developer resources
FeedbackBasket agent guide
Read when to use FeedbackBasket, the recommended agent workflow, credential boundaries, recovery links, and machine-readable resource locations.
Open resourceFeedbackBasket OpenAPI 3.1
Read typed REST operations, parameters, request bodies, response schemas, operation IDs, authentication rules, and structured errors.
Open resourceFeedbackBasket MCP server
Connect over Streamable HTTP. Version 3.1.0 provides all 31 product tools with browser OAuth or existing key access.
Open resourceFeedbackBasket MCP server card
Discover the canonical FeedbackBasket MCP endpoint, transport, protocol versions, repository, and product identity before connecting.
Open resourceFeedbackBasket CLI and authentication
Install the CLI, authenticate with a private token, use agent-safe JSON output, and manage projects and feedback from a shell-capable agent.
Open resourceFeedbackBasket webhooks
Receive signed feedback.created events with stable delivery IDs, raw-body HMAC verification, safe retry behavior, and endpoint security controls.
Open resourceAuthentication
REST API and CLI requests use a private CLI bearer token. Remote MCP can use browser OAuth or an existing MCP key. Read access permits queries. Writes need Full access and an organization owner or administrator role. Selected projects limits access to the approved projects. All projects includes projects created later and is required for project creation and team operations. High-impact MCP calls need explicit confirmation. Never put an access token, refresh token, CLI token, MCP key, session cookie, or webhook secret in browser code, generated application configuration, logs, prompts, or final agent output. Public discovery resources and the API health check do not need a credential.
Remote MCP setup
Connect an MCP host tohttps://feedbackbasket.com/.well-known/mcpwith Streamable HTTP. Save the server, select Authenticate, sign in, review the organization and access choices, and select Allow. Read is the default. Full needs an explicit choice. Selected projects does not include other projects. All projects includes current and future projects. Use an API key for STDIO MCP, CI, servers, or unattended automation. Keep all credentials out of source, command arguments, logs, prompts, and output.
REST API rate limits
Documented agent API routes allow 120 requests per minute for each client and route. Responses include the current structuredRateLimitvalue and theRateLimit-Policypolicy. Compatibility headers report the limit, remaining requests, and reset time. A 429 response also includesRetry-Afterin seconds. Agents must wait for that interval and use bounded backoff instead of retrying immediately.
Versioning and deprecation policy
Stable REST operations use a major version in the URL, such as/api/v1. Backward-compatible fields and operations can be added within that major version. FeedbackBasket will publish a replacement path and migration guidance before it removes or changes a stable operation. A deprecated response will use the RFC 9745Deprecationheader and a deprecation link. If an operation will stop working, it will also include aSunsetheader. Active v1 operations are not deprecated and therefore do not send false deprecation or sunset dates.