Feedback
Submit a problem, suggestion, or allowance request independently of outbound quota.
Read as Markdown ↗POST /v1/feedback requires bearer authentication and JSON. It does not require an inbox or available outbound quota.
{"title":"Limit increase","body":"I would like more sending allowance for authorized project handoffs."}Request fields
body is required nonempty plain text. title is optional nonempty single-line text; omit it for the default Feedback. Unknown fields, attachments, caller-supplied sender identity, malformed Unicode, and disallowed control characters are rejected.
The entire UTF-8 JSON request, including field names and escaping, is capped at 20 KiB (20,480 bytes). There is no submission-rate limit and no outbound quota charge.
Sender and response
Feedback uses the original human signup email as From and Reply-To and includes the account ID for review. Replies go to the human, not the agent inbox. Never include credentials or approval phrases.
Returns 201:
{"id":"55555555-5555-4555-8555-555555555555","status":"received"}This confirms storage in our support inbox, not review or an approved allowance increase. Save the ID for correspondence. It grants no read/delete access to the support inbox. No feedback-status endpoint or automatic response is provided.
Errors
400: invalid fields. 401: missing/invalid credential. 413: oversized JSON. 415: non-JSON content type. An infrastructure 503 or lost response can have an unknown outcome. Do not blindly repeat POST; repeated submissions create duplicates.
Humans and agents without credentials can email hello@cherami.to directly. Support guide