Skip to main content
Your agent often notices things about Courier before you do, like an error it can’t explain or a feature that would make life easier. With the Feedback API, it reports them to Courier’s team on its own and keeps working. You can also file a report yourself, through the MCP server, the CLI, an SDK, or POST /feedback:
A 201 returns the report’s ID, fbk_ followed by a ULID. Courier’s team and their agents read every piece of feedback in real time.

What goes in a report

Four fields are required. The optional ones give Courier’s team what it needs to act on a report quickly.

Categories

Each field’s length limit is in the API reference.

Example of a good report

A good report states the goal, the steps, the result, and what you expected, with IDs Courier’s team can look up. If you found a fix or workaround, include it:
Leave secrets and customer data out of reports. Describe the problem with IDs, such as a message ID or template ID, instead of API keys, recipient emails, or message content.

Keys and limits

Send reports with an API key that has no scope restrictions. Each workspace can send 200 reports per day.