MACO APP DOCS
  1. API Docs
MACO APP DOCS
  • Kundendokumentation
    • Oracle
      • API Docs
        • Overview
        • Error codes
        • Changelog Interfaces
        • Business Objects
        • Integration Layer
        • Trigger Events (MACO APP)
          • Role Supplier (LF)
            • Start of delivery
        • Read BO4E (Backend)
          • Get Communication Data
          • Get Meter
          • Get Tranche
          • Get Technical Resource
          • Get Controllable Resource
          • Get Grid Usage Contract
          • Get Grid Location
          • Get Metering Point Operation Contract
          • Get Meter Location
          • Get Market Location
          • Get Location Bundle
          • Get Meter Readings
          • Get The Load Profile
          • Get Energy Amount
          • Get Energy Supply Contract
          • Get Balance Sheet
          • Get CalculationFormula
          • Get Avis
        • Read Process Data (Backend)
          • Get Allocation Authorization
        • Write Process Data LF (Backend)
          • Create Process Data
          • Update Process Data
      • Process Docs
        • Supplier
          • Start of delivery (Role supplier new)
            • Process overview
  1. API Docs

Error codes

Interface Error Codes Overview#

Response Codes#

The MACO APP relies on standard HTTP status codes to indicate the success or failure of requests within the energy market communication process.
2xx HTTP codes signal successful processing of a request.
4xx HTTP codes indicate incorrect or incomplete input from the client side (market participant).
5xx HTTP codes reflect issues on the MACO APP server side (market communication platform).

Status Codes#

Status CodeDescription
200Request successfully processed.
4xxClient error – see error codes.
5xxServer-side error within MACO APP.

Error Schema#

MACO APP uses standard HTTP codes to represent the outcome of market communication requests. The following error codes may occur in communication processes with energy sector participants:
Status CodeTypeDescription
400malformedThe request contains syntax errors, e.g., an unreadable JSON payload.
401unauthenticatedThe request does not contain valid authentication credentials.
403permissionDeniedThe authenticated market participant is not authorized for this operation.
404notFoundThe requested resource is not available (e.g., process reference missing).
409conflictThe request conflicts with another request (e.g., duplicate transaction).
422invalidThe request contains invalid parameters or values.
429rateLimitedToo many requests in a short period – client temporarily blocked.
500internalAn unexpected system error occurred; the outcome is undetermined.
501notImplementedThe requested operation is not supported or not implemented.
502badGatewayThe server received an invalid response from an upstream service.
503unavailableService is temporarily unavailable (maintenance or system overload).
504timeoutNo timely response received from the upstream service.
505httpVersionNotSupportedThe HTTP version used is not supported by the server.

Error Handling#

When an error occurs, MACO APP provides additional details in the response payload.
This enables market participants and IT service providers to quickly identify and address the cause of failed market communication (e.g., faulty message format, authorization issue, or system downtime).
Modified at 2025-09-19 06:33:14
Previous
Overview
Next
Changelog Interfaces
Built with