Documentation menu
POST/v1/jobs/replan
API key required, sent as Authorization: Bearer snk_… or ?api_key=snk_….
Call it
curl -fsS -X POST "https://api.mapmap.ai/v1/jobs/replan" \
-H "Authorization: Bearer $MAPMAP_KEY" \
-H "Content-Type: application/json" \
-d @request.jsonRequest body
application/json
Exactly the POST /optimise/replan body: the original /optimise problem plus progress and changes, with an optional webhook_url. Metered on the REMAINING problem, exactly as the synchronous endpoint is, at the SN_OPTIMISE_MAX_LOCATIONS_ASYNC (2,000) ceiling rather than 200. Nothing is stored between calls here either: the async lane holds the submitted body until its retention TTL so it can run and serve the result, and that is the whole of it
The OpenAPI document declares this body as a free-form JSON object with no field list, so there is nothing here to generate a table from. The prose above is what the gateway states about it; the raw document is the authority.
Responses
result_url, or wait for the signed webhook| Field | Type | Required | Description |
|---|---|---|---|
| id | string | yes | The job id to poll. |
| kind | string | yes | optimise, replan or matrix. |
| result_url | string | yes | Where to fetch it. The same URL the webhook will carry. |
| status | string | yes | Always queued — the worker has not looked at it yet. |
| units_charged | integer | yes | Quota units this submission drew. Charged now, refunded in full if the job fails. |
webhook_urlwebhook_url was given but the key has no webhook signing secretSN_OPTIMISE_MAX_LOCATIONS_ASYNC unique locationsError bodies follow the shared problem model documented on API conventions.
Also under routing
Generated from https://api.mapmap.ai/openapi.json on 2026-09-17 · operationId post_replan_job