Error codes

Every code a Medos Developer API problem document can carry. Each one is the page its type URI points at.

StatusCodeMeaningRetry?
401UNAUTHENTICATEDThe key was not accepted.No
403IP_NOT_ALLOWEDThe calling address is not on the key's allowlist.No
403ROUTE_NOT_AVAILABLEThe path is not one of the Developer API's seventeen routes.No
403FEATURE_NOT_ENTITLEDThe workspace's plan does not include this route.No
400INVALID_ACTING_USERX-Acting-User-Id is not an MDU_… staff id.No
403ACTING_USER_NOT_A_MEMBERThe acting user is not an active member of this workspace.No
400END_USER_REQUIREDNot returned by any Developer API route.No
400VALIDATION_FAILEDThe request body failed validation.No
400UNKNOWN_FIELDA parameter or body field the route does not accept.No
400INVALID_PARAMETERA value is malformed, out of range, or names something this workspace does not have.No
404NOT_FOUNDNo such record in this workspace, or a /v2 path.No
409CONFLICTThe write conflicts with an existing record.After re-reading
405METHOD_NOT_ALLOWEDThe path exists, but not with this method.No
415UNSUPPORTED_MEDIA_TYPEThe request body is not JSON.No
406NOT_ACCEPTABLEThe Accept header allows nothing this API produces.No
429RATE_LIMITEDOver a rate limit.Yes
4xxUPSTREAM_REJECTEDThe Medos core refused the request.No
502UPSTREAM_UNAVAILABLEThe Medos core failed or did not answer.Yes
500INTERNAL_ERROROur fault.Yes

How the problem document is shaped, and how to handle each family of errors: Developer API errors.