Skip to main content
Run a test against ChargerDojo’s sandbox to see how checks and reports work. You need a browser, with no account, payment card or API key. The sandbox is ChargerDojo’s OCPI peer. This run tests that peer, not your implementation. To test your own or a partner’s service, connect an endpoint on Integrate or above.

Open a saved report first

Open the saved example report. It is a captured OCPI 2.2.1 roaming-hub journey against ChargerDojo’s reference endpoint. It is a passing example with some ungraded checks, not evidence about your endpoint. Check the version and scope, then expand an exchange to see the request, response and associated checks. Read and diagnose a report explains what to inspect when a check fails.

Run your own sandbox test

  1. Open Testing.
  2. Under You build, choose CPO, eMSP or PTP service, then choose an OCPI version. The endpoint selector switches to the matching sandbox, such as Sandbox CPO. CPO means charge point operator; eMSP means e-mobility service provider; PTP means payment terminal provider. The glossary explains their responsibilities.
  3. Choose Run tests. The selected sandbox is the system under test; ChargerDojo’s tester plays its counterparty. To run one module, open Conformance and manual requests under Working tools.
  4. Wait for the run to finish, then choose View report. Read the coverage and counts before treating a green result as a pass for your chosen scope.
  5. Expand a check that sent a request. Compare the recorded response with its expected result, then follow its specification citation where one is recorded.
A check marked Not tested has no graded evidence. Not applicable means the rule is outside this endpoint’s responsibilities. Neither is a failed requirement. Report guidance explains the distinction.

Keep or share the result

Find the report in Runs. Your browser’s anonymous session retains access until the session expires or its stored data is cleared, within report retention. Signing in attaches this browser’s reports to your organisation for access from other devices. Share a report if someone else needs to inspect it without an account. Inspect its payloads before sharing.

Test your endpoint next

Read what ChargerDojo tests to check version, module and interface support. Then connect your endpoint and run a suite. The API quickstart is the equivalent automation path once you have a paid API key.