API Error Codes | Mappinest Docs

Look up shared HTTP statuses and API-specific error tables below.

HTTP status codes

Code	Description
400	Invalid request path, parameters, headers, or body.
401	Missing API key.
402	Unpaid invoice after the payment grace period.
403	API key, scope, domain policy, or resource access denied.
404	Resource or public route not found.
405	Unsupported request method.
409	Revision conflict or another active operation.
410	Retired `/styles` endpoint. Use `/v1/maps`.
412	The ETag belongs to a different resource.
413	Upload, body, operation count, or resource exceeds its limit.
415	Unsupported content type or rendered map raster format.
422	Invalid data, geometry, or request parameters.
428	Required `If-Match` header is missing.
429	Request, upload, or monthly quota limit reached.
500	Internal service error.
502	Unable to retrieve the resource from an upstream service.
503	Service or request protection temporarily unavailable.
504	An upstream service timed out.

Tiles API, Maps API, and Dataset API errors return JSON with error.code and error.message.

Missing API key response

{"error":{"code":"API_KEY_REQUIRED","message":"An API key is required"}}

Error code	HTTP status	Description
`INVALID_REQUEST`	400	Check the request path and parameters.
`UNSUPPORTED_MEDIA_TYPE`	415	Use a format supported by the endpoint.
`UNPROCESSABLE_REQUEST`	422	Check the request parameters and resource format.
`INTERNAL_ERROR`	500	Retry later or check the service status.
`UPSTREAM_ERROR`	502	The resource could not be retrieved. Retry later.
`SERVICE_UNAVAILABLE`	503	The service is temporarily unavailable. Retry later.
`UPSTREAM_TIMEOUT`	504	The upstream service timed out. Retry later.

Honor Retry-After when provided. Resolve quota and payment blocks in Billing.

See Dataset API Errors for codes and recovery steps.