Changelog

October 16, 2026

Highlights

• Confirmation run — The official conformance run for your Lifecycle API. It runs the complete test suite for the selected system role. If your API passes, you receive a PDF confirmation by email. The confirmation can also be downloaded from the result page.
• Profiles — Test runs and confirmation runs now use the BatteryPass of the selected profile: its schema, sample battery passports and access rights. Choose a predefined profile for your battery category (EV, LMT, etc.) or one of your own.
• Access Right Editor — You can use the Access Right Editor to change the default access control for each data element to match your system under test.
• New system role: Main Service Provider — A system role for service providers that run battery passports on behalf of several economic operators.
• Test run history — The history keeps the test logs of your test runs, so you can analyze them later. Up to 50 test runs per user are kept; when the limit is reached, the oldest run is removed.

Action required

• New BatteryPass schema version 2.0.1.
• API version — you now choose whether a run targets the versioned routes (/v1/...) defined by the standard or the unversioned draft routes. The base URL must not contain a query or fragment.
• Your system must reject invalid updates with status code 400, and updates that do not change the content with status code 409.
• If a role lacks the required permission, the test environment now expects status code 403.
• ReadDPPById now returns the battery passport regardless of its status (active, archived or marked for deletion). ReadDPPByProductId still returns only the active passport.
• An update that changes a data element not marked as stable creates a new battery passport with a new DPP ID. The previous passport is archived and can still be read by its old DPP ID.
• A read without credentials returns the public view of the battery passport. Credentials that cannot be verified are rejected with status code 401, and so is creating a battery passport without credentials.
• Only battery passports marked for deletion can be deleted. Deleting an active passport must be rejected with status code 409.
• Multiple economic operators — the test adapter command issueCredentials has a new optional field economicOperatorId. Access to a battery passport of another economic operator must be rejected with status code 403.
• EU Registry — the registration now uses the field names of the standard: uniqueProductIdentifier, digitalProductPassportId, uniqueEconomicOperatorIdentifier, uniqueEOIdentifierBackupOperator and dppApiEndpoint (an absolute URI). The previous fields Product_ID, Backup_ID and Operator_ID are no longer accepted.

New

• Knowledge section — the start page explains the digital battery passport and the requirements of the regulation, and answers frequently asked questions.
• Batch runs — several or all test cases of your system role run in one pass, with a progress display and the option to cancel.
• Result page — every test run now has a dedicated page with an overview, filters and the configuration used.
• Test results can be copied and downloaded, individually as a JSON file or together as a ZIP archive.
• Test runs can be deleted from the history, which now shows more details about each run, including its type.
• Changelog — the changelog now has its own page that lists all updates.
• The user menu now takes you straight to your account management.
• An unknown address or an unexpected error now shows a clear error page with a way back.
• New test cases cover creating and deleting battery passports, retrieving an earlier state, looking up passports by product identifier, reading the public view without credentials, rejecting access across economic operators, missing or unknown data elements, and the new DPP ID after an update.

Improved

• Validation schemas — the selection in data validation is now sorted into folders by data model and version.
• User documentation — the structure of the test environment is now shown as a clearer diagram, and the resource list points to further API documentation.
• Header — signing in now has its own button, and the test environment is now marked as a beta version instead of a prototype.
• When comparing values, the expected and the actual side are now clearly labeled.
• An unexpected status code now counts as a failed check instead of an error in the test run.
• Credentials and tokens are now redacted in the logs of the test results.
• Error messages no longer reveal internal details.
• You can keep up to 20 profiles of your own.

Fixed

• After switching the system role, results and selections from the previous run are no longer carried over.
• The selected profile stays selected after the page is reloaded.
• Test setup is now shown as failed when your test adapter rejects a single command. Previously it still appeared green.
• Copying a test result now works even when you open the test environment over an unsecured connection.
• Public pages now load even when the sign-in service is unreachable.
• Floating page controls no longer cover open dialogs.
• The notice about new changelog entries no longer reappears after switching the language.
• Pages now display correctly on any screen size without unwanted horizontal scrolling, and new pages open at the top again.