Skip to main content
ChargerDojo sends OCPI requests to a selected endpoint and grades the evidence its checks inspect. A report covers that endpoint, version and selected scope. It does not establish every behaviour of an implementation. Try a free browser test against ChargerDojo’s sandbox to inspect the evidence. A sandbox result concerns ChargerDojo’s peer. Testing your own or a partner’s endpoint needs Integrate or above and registration.

Versions and interfaces

The app offers OCPI 2.1.1, 2.2.1 and 2.3.0. The API also accepts the 2.2 compatibility version, which is not selectable in the app. Choose the version the endpoint actually runs. A module advertised for a version has a conformance suite. Before running it, check which interfaces the endpoint advertises. A CPO or eMSP is a business role; Sender and Receiver identify a module’s data interface. They do not say who starts registration. Use the suite catalogue to inspect the checks for your version and role. A conformance suite checks protocol rules. A charging journey follows a timed interaction and separates OCPI requirements, business checks and observations in its report.

Extensions

Direct Payment is a separately published extension on OCPI 2.2.1 and part of the core specification on 2.3.0. Bookings on 2.3.0 follows the separately published 2.3.0-booking-1.1 document. See payment-terminal testing for the applicable roles and plan.

Sandbox limits

ChargerDojo’s conformance and internal parity tests do not provide external OCPI certification. ChargingProfiles serves the Receiver interface only on 2.2.1. Its Sender interface is not implemented. The sandbox also serves only the Receiver interface for ChargingProfiles on 2.2 and 2.3.0. UNKNOWN-LOCATION and UNKNOWN-EVSE always answer REJECTED, and UNKNOWN-SESSION always answers UNKNOWN_SESSION, so you can exercise the rejection paths on purpose. From 2.2 onward, the sandbox keeps Sender-owned and Receiver-owned data separate. An object pushed to a Receiver URL does not become an object on the sandbox’s Sender list. On 2.1.1 those stores still merge. Older 2.3.0 CDRs stored before that separation can still appear on the Sender list; newly pushed CDRs stay separate. The sandbox enforces ownership. Name a party your credential did not register in a client-owned URL and the sandbox answers a miss, on every version, as a real receiver may. On 2.2, 2.2.1 and 2.3.0 the sandbox keeps every object a run pushes, Commands aside, across ChargerDojo releases. On 2.1.1 it does not yet keep pushed objects through a release. Each sandbox keeps its own objects, apart from your other sandboxes and other accounts. Signed in, the sandbox card on the Endpoints page counts stored objects and offers Clear pushed objects; the sandbox’s seed data returns on the next request. On 2.2.1 and 2.3.0 the count and the clear leave out Payments Terminals and Financial Advice Confirmations, and on 2.3.0 also Sessions, CDRs, Tokens and Bookings, which are kept for up to 90 days. The card says so under the count. Sandbox credentials are provisioned directly rather than exchanged through a loopback credentials handshake. Use a registered external endpoint when you need evidence about registration with your implementation.

How checks are tested

Deliberately broken peers test whether checks detect the defect they are meant to find. Conformance checks, scenario walkthroughs and charging journeys have separate mutation sweeps. Their scope and exemptions differ; a passing sandbox demonstration alone does not prove every check can detect every possible defect. Internal parity tests run the tester against ChargerDojo’s own routes. This checks that those routes and suites agree. It does not replace interoperability testing with another implementation or external certification.

Read the result within its scope

A failed required rule needs investigation. Warnings identify recommendations or observations and do not increment the failed-check count. Not tested means no graded result; not applicable means the rule is outside this endpoint’s responsibilities. Read the recorded reason before deciding what remains to test. Read your report to follow a finding to its exchange and applicable clause. A partner agreement is a separate authority from OCPI; a product policy is not an OCPI requirement.