POST/map-issues

API key required, sent as Authorization: Bearer snk_… or ?api_key=snk_….

Call it

bash

curl -fsS -X POST "https://api.mapmap.ai/map-issues" \
  -H "Authorization: Bearer $MAPMAP_KEY" \
  -H "Content-Type: application/json" \
  -d @request.json

Request body

application/json · CreateMapIssueRequest

Field	Type	Required	Description
category	string	yes	One of [`CATEGORIES`], e.g. `"restriction-wrong"`.
contact	string	no	Optional contact email for follow-up (trimmed, at most 200 bytes; length-checked only).
heading_deg	number	no	Direction of travel in degrees clockwise from north, `0 <= x < 360`: the route's bearing at the reported position. Required for the `traffic-*` categories, optional otherwise.
lat	number	yes	Latitude of the problem, decimal degrees (WGS84), within [-90, 90].
lon	number	yes	Longitude of the problem, decimal degrees (WGS84), within [-180, 180].
note	string	no	Optional free-form description (trimmed, at most 1000 bytes).

Responses

201Report stored for triage

Field	Type	Required	Description
id	string	yes	Report id (UUID v4).

400Invalid category, out-of-bounds coordinates, over-long note/contact, heading_deg out of range, or a traffic report without heading_deg

401Missing or invalid API key

429This key has hit its daily report cap

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

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