Documentation menu
self-serve
GET/v1/jobs/{id}
API key required, sent as Authorization: Bearer snk_… or ?api_key=snk_….
Call it
bash
curl -fsS -X GET "https://api.mapmap.ai/v1/jobs/{id}" \
-H "Authorization: Bearer $MAPMAP_KEY"Parameters
| Name | In | Required | Description |
|---|---|---|---|
| id | path | yes | Job id from the submission's 202 |
Responses
200The job:
status, and result inline once it is succeeded| Field | Type | Required | Description |
|---|---|---|---|
| created_at | string | yes | RFC 3339 UTC submission time. |
| error | string | no | Why the job failed, once status is failed. |
| finished_at | string | no | RFC 3339 UTC time the job finished, either way. |
| id | string | yes | Opaque job id (UUID v4), as returned by the submission. |
| kind | string | yes | optimise or matrix. |
| refunded | boolean | yes | Whether a failure refunded the submission's units and pence. |
| result | not stated | no | The answer, inline, once status is succeeded. Exactly the body
the synchronous endpoint would have returned. |
| result_url | string | yes | Where to fetch this job (and its result) — the same URL the webhook carries. |
| started_at | string | no | RFC 3339 UTC time a worker picked the job up. |
| status | string | yes | queued, running, succeeded or failed. |
| units_charged | integer | yes | Metered units the submission drew. Zero after a failure refund
would be a lie — this is what was CHARGED, and refunded says
whether it came back. |
| webhook_status | string | no | delivered or delivery_failed once a webhook was attempted. |
401Missing or invalid API key
404No such job for this caller; including a job that belongs to somebody else, and one whose result has passed its retention TTL
Error bodies follow the shared problem model documented on API conventions.
Also under self-serve
Generated from https://api.mapmap.ai/openapi.json on 2026-09-17 · operationId get_job