We’ve been adding new enhancements to the ecosio.api.

1. New endpoint for e-invoicing documents
   
   This new endpoint provides all necessary e-invoicing documents for a specific messageId within one request.

   
   

   

   
   The .zip file includes the original invoice, providing a detailed record of the transaction. You'll also find the acknowledgment, which serves as key evidence confirming the receipt and understanding of the invoice. The content of the .zip folder may vary depending on the country.

   

   This document indicates the completion of the invoicing process and serves as the final record of the transaction. These documents collectively provide a complete picture of each transaction, ensuring you're well-equipped for any future inquiries or audits.

   
   

   

   
   

2. Log informations for e-invoices
   
   We added the log information for e-invoices to governments/clearing centres into our "GET MESSAGE STATUS" request. When crafting your request, you only need to add `’"includeLog" = true’ into the header.
   

   

   By including this parameter, you ensure that any issues can be traced and resolved efficiently, thereby improving the overall reliability and transparency of your e-invoicing process.
   

   

   Additionally, the detailed logs can serve as a valuable resource for auditing and compliance purposes, as they offer a comprehensive history of all interactions and responses. This can be particularly helpful for meeting regulatory requirements or for internal assessments. Ensuring that these logs are included in your "GET MESSAGE STATUS" request will not only aid in troubleshooting but also in maintaining a robust and compliant e-invoicing system.
   

   As e-invoicing requirements continue to evolve, we are committed to providing solutions that enhance your experience and ensure that you meet all necessary regulations. Including log information is just one of the many ways we strive to support your e-invoicing needs effectively.
   

Bug Fixes in the OpenAPI spec
(the behaviour of the ecosio Integration HUB did not change):

• We fixed the returned objects for Error Codes 401, 404, 413, 429 and 500

• Reduced duplicated description

• “Get List Messages” - type changed from string to integer

• “Post Archive” - type changed from integer to string

• “Get Message Status” - type changed from string to integer

• Added the missing fields in the returned object of the 200 response on the “GET Archive ID” request

• Fixes timezones in data examples

• Fixed messageIds

• Include acknowledgment schema in “POST Archive” request

• Fixed type for “numMessagesArchived” and “numFilesArchived”

• Changed Archive Status response from integer to string

• Fixed information about multi tenant and added example

• Refactoring of existing error schemas