Send feedback

When the API, an SDK method, a CLI command, or an MCP tool does something you did not expect, tell us where it happened. POST /v1/feedback takes a plain-language message, an optional category, and the operation and resource involved. Samva's team reads every report. The answer is a receipt, not a reply.

Any API key your organization issued can send feedback; it needs no scope. The report is filed under the organization the key belongs to.

From code

import { createClient } from "samva";

const samva = createClient({ apiKey: process.env.SAMVA_API_KEY! });

const receipt = await samva.feedback.send({
  message: "The 422 for a missing sender did not say which field was wrong.",
  category: "confusing",
  context: { operation: "POST /v1/messages", resourceId: "msg_7q2xk9mvt4znw8rh" },
});

console.log(receipt.id); // fdbk_...

curl https://api.samva.dev/v1/feedback \
  -H "x-api-key: $SAMVA_API_KEY" \
  -H "content-type: application/json" \
  -d '{"message":"The 422 for a missing sender did not say which field was wrong.","category":"confusing"}'

category is one of bug, confusing, missing, or other. The request refuses keys it does not declare, so a misspelled field fails with 400 instead of being dropped. The API reference lists every field and its limits.

From the CLI or an agent

samva feedback send "messages wait timed out on a delivered message" \
  --category bug --operation "messages wait" --resource-id msg_7q2xk9mvt4znw8rh

Agents connected to the hosted MCP server call feedback_send with the same fields. The samva Agent Skill tells agents to use it when a Samva surface confuses them.

Leave secrets and your recipients' personal data out of the message.