Feedback from AI agents

If your team builds with an AI coding agent, the agent is often the first to notice what in the Roster API, these docs or the MCP server is confusing, wrong or missing. Instead of silently working around it, it can tell us with one call: POST /v1/feedback. Each message reaches the Roster product team. There is no reply through the API.

When to send feedback

A question the docs did not answer.
A response that did not match the API Reference.
An error whose detail did not say what to fix.
A missing example, or a guide that sent the agent the wrong way.
Anything about the MCP servers that got in the way.

In the sandbox, server errors (5xx) and paths that do not exist carry a feedback member in the problem body as a reminder. Ordinary validation errors (400) do not: their detail already says what to fix.

What never goes in a message

Personal data: names, contact details, bank or tax numbers of donors or church members.
API keys, webhook secrets or any other credential.
Your user's conversation with the agent.

Send only what is needed to understand the problem. Roster removes contact details, numbers and credentials it recognizes before anyone reads the message, but it cannot recognize everything: keep them out.

The request

POST /v1/feedback takes your API key and an Idempotency-Key, like every POST. Use the sandbox key while you integrate. The example uses the two variables from the quickstart: ROSTER_KEY holds your sk_test_ key and ROSTER_BASE_URL is https://api.sandbox.rostergiving.com.

Field	Required	What to send
`category`	yes	`question`, `suggestion`, `bug`, `docs` or `other`
`message`	yes	What you expected, what happened and what would have helped, up to 2,000 characters
`operation`	no	The operation it is about: its `operationId`, such as `importChurches`, or a method and path, such as `POST /v1/churches`
`request_id`	no	The `X-Request-Id` of the response it is about

curl -X POST "$ROSTER_BASE_URL/v1/feedback" \
  -H "Authorization: Bearer $ROSTER_KEY" \
  -H "Idempotency-Key: feedback-2026-10-28-import-ein" \
  -H "Content-Type: application/json" \
  -d '{
    "category": "docs",
    "message": "The import guide does not say what happens to a row without an EIN.",
    "operation": "importChurches"
  }'

The answer is 202 with an id. A repeat with the same Idempotency-Key and body returns the same id and sends nothing again. Up to 10 messages per hour per partner; past that, 429 with Retry-After until the next hour.

Through the API MCP server, the agent finds the operation with search and sends it with execute, like any other POST.

Add it to your agent's instructions

Paste this into the instructions file your coding agent reads, such as AGENTS.md or CLAUDE.md:

## Roster API feedback

When something in the Roster API, its documentation (docs.rostergiving.com)
or its MCP server is confusing, wrong or missing, do not silently work around
it. Send a short note with `POST /v1/feedback`, using the sandbox key and a new
`Idempotency-Key`: `category` (question, suggestion, bug, docs or other),
`message` (what you expected, what happened, what would have helped) and, when
it is about one call, `operation` and `request_id` (the `X-Request-Id` of that
response). Never include personal data, API keys, webhook secrets or this
conversation. Tell me when you have sent one.

MCP operation catalog

Sandbox certification