Product Updates

Release summary

This release adds e-invoicing scenarios for France and the United Kingdom. It also introduces OAuth2 authentication as the recommended authentication method for Management API integrations.

🌍 New country scenarios

Partners can now activate two additional country scenarios through the Management API:

• 🇫🇷 France

• 🇬🇧 United Kingdom

These scenarios provide the country-specific configuration required for customer onboarding and reduce manual setup.

Endpoint

POST /api/v1/management/companies/{companyUuid}/scenarios

🇫🇷 France example

{ 
"name": "FRANCE_EINVOICE", 
"peppolParticipantIds": ["9957:FRxxxxxxxxx"], 
"emailAddressesForValidationErrors": ["user@company.com"], 
"siret": "xxxxxxxxxxxxxx", 
"siren": "xxxxxxxxx", 
"paAuthorisationContract": true, 
"direction": "BOTH", 
"selfBilling": false 
} 

🇬🇧 United Kingdom example

{ 
"name": "UNITED_KINGDOM_EINVOICE", 
"peppolParticipantIds": ["9932:GBXXXXXXXXX"], 
"emailAddressesForValidationErrors": ["user@company.com"], 
"direction": "BOTH" 
} 

🔐 OAuth2 authentication

The Management API now supports the OAuth2 client credentials flow. OAuth2 is the recommended authentication method for new integrations.

The required credentials are:

• Client ID

• Client Secret

• App key, which remains unchanged and is still required with OAuth2

Authentication options in Monitor

Monitor now provides both authentication methods for Management API connectors:

• Basic Authentication, which still requires IP whitelisting

• OAuth2 client credentials, which does not require IP whitelisting

The OAuth2 credentials are available below the connector information in Monitor. Select the option to generate your new Client ID and Client Secret. Copy the Client Secret when it is generated and store it in an approved credential manager, as it is hidden afterwards.

⚠️Migration period

Both authentication methods are currently available. Basic Authentication is marked for deprecation, but no removal date has been announced. Existing integrations can continue to use Basic Authentication during the migration period. OAuth2 is recommended because it removes the need for IP whitelisting.

✅ Recommended action

• Use OAuth2 for new integrations

• Plan the migration of existing integrations from Basic Authentication to OAuth2

• Keep the existing app key in every request

🔭 Next up

We are preparing additional country features for:

• 🇸🇰 Slovakia

• 🇭🇷 Croatia

• 🇦🇪 United Arab Emirates (UAE)

• 🇩🇪 Germany e-mail scenario

The ecosio Product team

🚀 What’s new

1. Peppol Scenario Support (multi-country)

Partners now have access to support for a set of Peppol-based scenarios that can be activated via the Management API.

Countries included:

• Germany

• Norway

• Belgium

• Sweden

• Netherlands

• Finland

• Estonia

• Denmark

Example: Peppol Belgium scenario payload

{ 
"name": "BELGIUM_EINVOICE", 
"peppolParticipantIds": "2090:BExxxxxxxxx", 
"emailAddressesForValidationErrors": "test@ecosio.com", 
"direction": "BOTH" 
} 

2. Test-only flag (usedForTestOnly)

We introduced the optional parameter usedForTestOnly = true to clearly mark entities created via the Management API as test data.

It can be applied to:

• Companies

• Connectors

• Scenarios

🔍 Why is it important?

This flag helps separate testing activities from real customer configurations, so internal teams can quickly identify non-production objects and handle approvals, visibility, and reporting accordingly.

The ecosio Product team

🚀 What’s new

Poland country scenario (enablement for existing customers)

Partners can now enable the Poland scenario for an existing customer created via the Management API.

Notes:

• Scenarios can only be added to companies that were created via the Management API.

• Two activation options are supported: KSeF token or certificate.

• Update functionality will be provided in a later release.

Endpoint: POST /api/v1/management/companies/companyUuid/scenarios

Request (KSeF token):

{ 
"taxNumber" : "TAX ID xxx", 
"ksefToken" : "xxx", 
"name" : "POLAND_EINVOICE" 
} 

Request (certificate):

{ 
"taxNumber" : "TAXIDxxx", 
"digitalCertificate" : { 
    "certificate" : [ xxx ], 
    "privateKey" : 
       { "key" : [ xxx ], 
         "passphrase" : "xxx" } 
}, 
"name" : "POLAND_EINVOICE" 
} 

Detailed documentation about the mandate in Poland: Compliance for Poland

🔁 What’s changed

Connector create endpoint field rename

To reduce confusion, we renamed the connector create field:

• apiKey → userKey

Applies to: POST /api/v1/management/connectors

If you create connectors via the API, update any client-side parsing and mappings that read or write the old field name.

Reference: Create connector endpoint

⏳Coming soon

• Monitor user scenario

• Peppol scenario

• Italy scenario

• Germany scenario

• Poland Update scenario

The ecosio Product team