Messaging APIDeliver messages to the HubGet the status of a delivered message from the ecosio Integration Hubget https://api.test.ecosio-hub.com:{port}/api/v1/delivery/{messageId}Path ParamsmessageIdstringrequiredThe UUID of the message, whose status shall be retrievedHeadersincludeAckbooleanDisplay the acknowledgment of a sent e-invoice to a government in Base64 and its external references. External references and their availability are country-specific. For a detailed list of availability per country, see External references for acknowledgements.truetruefalseincludeLogbooleanDisplay the logs of a message to review its details and history. This can help you understand the message's journey, including when it was sent, received, and any actions taken on it.truetruefalseResponses 200OK. The details of the sent messages. Among the details is also the state of every sent message. 400BAD REQUEST CodeNameDescription100APPLICATION_KEY_INVALIDThrown if either no or an invalid application key was provided110INVALID_JSON_MESSAGEIs thrown in case the request is invalid JSON111JSON_DOCUMENT_NOT_BASE64_ENCODEDIs thrown if the actual document is not properly base64-encoded within the message field of the JSON message.120EXPECTED_QUERY_PARAMETER_MISSINGIndicates that a required query parameter is missing in a request. Often this indicates that the appKey parameter is missing123QUERY_PARAMETER_UNKNOWNThe value of a provided query parameter is unknown to the service.200ARGUMENT_NULLIndicates that a required argument is null368DOCUMENT_NOT_VALIDMay be thrown by the service if the received document syntax is not valid 401UNAUTHORIZED In case the authentication credentials are not valid CodeNameDescription102CREDENTIALS_INVALIDThe provided credentials are invalid 403FORBIDDEN. In case the user could not be authenticated CodeNameDescription101USER_KEY_INVALIDThe user provided a wrong user key (deprecated)104USER_NOT_PERMITTEDThe user authenticated successfully but has no rights to fulfill the requested task 404NOT FOUND. In case the message could not be found 429TOO MANY REQUESTS. CodeNameDescription130TOO_MANY_REQUESTS_RECEIVEDIn order to prevent being spammed by poll requests and status queries the service makes use of a request cache. If the number of requests received in a certain amount of time exceed a certain threshold this error will be returned. Every 5 minutes the cache will be cleared automaticallyUpdated 7 months ago Whatās NextExternal references for acknowledgementsDid this page help you?YesNo