Mediloop
DocsAPIsSupplier APIErrors
Supplier API

Errors

The Mediloop APIs use standard HTTP status codes to indicate the outcome of a request. All error responses are returned in a consistent JSON format.

Error codes overview

HTTP StatusCodeTypeDescription
400BAD_REQUESTClient ErrorThe request is invalid or cannot be processed.
401UNAUTHORIZEDClient ErrorAuthentication is required or has failed.
403FORBIDDENClient ErrorYou don't have permission to perform this action.
404NOT_FOUNDClient ErrorThe requested resource was not found.
409CONFLICTClient ErrorThe request conflicts with the current state.
429RATE_LIMITEDRate LimitToo many requests. Please try again later.
500INTERNAL_ERRORServer ErrorAn unexpected error occurred on our server.
503SERVICE_UNAVAILABLEServer ErrorThe service is temporarily unavailable.

Error response format

{
  "success": false,
  "error": {
    "code": "INVALID_PARAMETER",
    "message": "The 'sku' field is required.",
    "details": "Missing required field: sku",
    "trace_id": "c1f2e3d4-5678-90ab-cdef-1234567890ab"
  }
}

Example responses

HTTP/1.1 400 Bad Request
Content-Type: application/json
X-Request-Id: c1f2e3d4-5678-90ab-cdef-1234567890ab

{
  "success": false,
  "error": {
    "code": "INVALID_PARAMETER",
    "message": "The 'sku' field is required.",
    "details": "Missing required field: sku",
    "trace_id": "c1f2e3d4-5678-90ab-cdef-1234567890ab"
  }
}

Common error codes

INVALID_PARAMETER

A required field is missing or invalid.

UNAUTHORIZED

Credentials are missing or invalid.

FORBIDDEN

The key lacks the required scope.

RATE_LIMITED

Wait until the rate limit resets.

Best practices

If you receive an error you can’t resolve, contact support with the trace_id and request timestamp; never send your raw API key.