Skip to content
Documentation menu
docs / api / post-v1-feedback-arrival
Feedback and map issues

POST/v1/feedback/arrival

Access and price

AuthAn API key, as Authorization: Bearer snk_… only. Not metered: it draws no quota and no credit. Needs a full key; a browser (maps) key is refused.
PriceNot metered: no quota, no credit.

What it does

Records one answer to "Did that get you there?". Answers 204 with no body.

An API key, as Authorization: Bearer snk_… only. Not metered: it draws no quota and no credit.

Call it

bash
curl -fsS -X POST "https://api.mapmap.ai/v1/feedback/arrival" \
  -H "Authorization: Bearer $MAPMAP_KEY" \
  -H "Content-Type: application/json" \
  -d '{"answer":"yes"}'

Request body

application/json · ArrivalFeedbackRequest

FieldTypeRequiredDescription
answerArrivalAnsweryesyes or not-quite.

Example: A request assembled from this schema's own field examples, enums, defaults and types; not a recorded call

json
{
  "answer": "yes"
}

Responses

204Counted (day, app and answer only)
400Anything but exactly {"answer":"yes"|"not-quite"}, or the key sent as ?api_key=

application/problem+json · Problem

401Missing, unknown, revoked or expired key. Also: No key, or a missing, malformed, unknown, revoked or expired one (unauthorized)

application/problem+json · Problem

403Not a MapMap app key. Also: A browser (maps-scoped) key on a route that needs a full-scope key (scope-insufficient)

application/problem+json · Problem

413The request declares a body larger than 1048576 bytes (plain text, not problem+json)

text/plain

429More than one answer from this key in five minutes

application/problem+json · Problem

504The request did not finish within the gateway's request deadline (request-timeout)

application/problem+json · Problem

Error bodies follow the shared problem model documented on API conventions.

Also under Feedback and map issues

Generated from https://api.mapmap.ai/openapi.json on 2026-11-18 · operationId post_arrival_feedback