Report an issue
POST /v1/feedback/issuesFreeWrites
Reports a problem on the public board: a failing or wrong API call (pass its request_id from the X-Request-Id header or the error's request_id, and the op), a wrong or missing boundary, a docs error, or anything else broken. Check list_feedback with kind=issue first and upvote a matching report instead. Free; needs a key; 10 new items per account a day. Only you see the request_id. Everything on the board is public (never the author's email). Do not include API keys, personal data or customer data.
MCP tool report_issue · CLI geocode report-issue · RPC POST /v1/ops/report_issue
Input
| Field | Type | Description |
|---|---|---|
titlebody, required | string | What is wrong, in one line. |
detailsbody | string | What you did, what you expected and what happened (status, error code, boundary id). Default "". |
request_idbody | string | The request_id of the failing call, if there was one. |
opbody | string | The op the failing call used, e.g. get_boundary. |
Example request
curl -X POST "https://geo-coder-service.vercel.app/v1/feedback/issues" \ -H "Authorization: Bearer $GEOCODE_API_KEY" \ -H "Content-Type: application/json" \ -d '{"title":"get_boundary returns 404 for r62422","details":"Berlin by relation id: 404 not_found since this morning.","op":"get_boundary"}'Example response
See the description above for what this returns.
Errors
Failures are RFC 9457 problems. Common ones here: 400 invalid_input, 401 unauthorized, 429 rate_limited.