Documentation menu
POST/v1/jobs/optimise
API key required, sent as Authorization: Bearer snk_… or ?api_key=snk_….
Call it
curl -fsS -X POST "https://api.mapmap.ai/v1/jobs/optimise" \
-H "Authorization: Bearer $MAPMAP_KEY" \
-H "Content-Type: application/json" \
-d @request.jsonRequest body
application/json
Exactly the POST /optimise body: vehicles, jobs, optional shipments, costing, costing_options, adr, eu_drivers_hours, plus an optional webhook_url. The unique-location cap here is SN_OPTIMISE_MAX_LOCATIONS_ASYNC (2,000 by default), ten times the synchronous 200: the synchronous cap is bound by the request deadline, and there is no request to hold open here
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_url (must be https and publicly resolvable)webhook_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_optimise_job