Skip to main content
Issue a registration token when the endpoint under test will start the credentials handshake. ChargerDojo receives its credentials, calls back to its advertised URL and records the connection. You need Integrate or above, an available partner-endpoint slot and permission to add an endpoint. If you already hold the endpoint operator’s registration token and want ChargerDojo to start the exchange, connect an endpoint instead. You need this when your partner wants to prove their client works, not their server. It is also the direction to use when a partner asks you for Token A: in OCPI the receiving party issues it, so if they are asking, they mean to register with ChargerDojo. See OCPI 2.2.1 registration.

Issue a token

Under Testing, open Endpoints, then choose Add an endpoint, or Add endpoint once you have one. Choose the system under test and select It registers with ChargerDojo. Pick the OCPI version it runs and answer whether it is a test system or production, then choose Issue a token. That answer controls later runs, not the credentials handshake. The picker offers 2.1.1, 2.2.1 and 2.3.0. The API accepts 2.2 as well, and suites run against it, but no picker in the app offers it. See version coverage. Pick the version they actually run, not the newest one. The token is recorded against that version, and a client that speaks a different one will not finish the handshake against it. You get four values. Send all four, together, over whatever channel you already use with that partner. The specification puts this exchange deliberately outside the protocol, so there is no OCPI-blessed way to deliver them.

How they send the token

The credentials token is transported differently across versions. On 2.1.1 it goes in the header as it is; from 2.2 onwards the header carries the Base64 of it. The issued-token panel shows the exact header for both forms, so you can paste the one they need rather than describe it. An unencoded token on a 2.2 or later endpoint returns 401. The issued-token panel shows the expected header; when the token is correct but its encoding is wrong, the connection names that error. Sources: OCPI 2.1.1 request format and OCPI 2.2.1 Authorization header.

What happens when they register

Setup succeeds when the row says Registered. This confirms the credentials exchange, not a conformance verdict. Their client reads the versions URL, picks its version, and POSTs its credentials to ChargerDojo’s credentials endpoint. ChargerDojo then calls back to their versions URL with the token they just sent, reads their endpoints, and only then records the registration. That callback is part of the handshake, so their endpoint has to be reachable from the internet for it to finish. If it runs on a laptop or inside a VPC, put a tunnel in front of it. A local connector does not carry this incoming registration callback, even when it runs beside your own service. The row reads Waiting for them until their POST arrives, which means the token is issued and unused and nothing is due from you, then Registered once the handshake finishes and they hold a live credentials token. Until it does ChargerDojo does not know who they are, so the row shows no party. That is the expected state, not a stuck one.

Reading the token back, and taking it away

While a row is still waiting, Show token returns the registration token you issued, so you do not have to keep a copy outside ChargerDojo. Once they register, the handshake has spent that token and there is nothing left to show. Their system now holds its own credentials token instead. Revoke ends the registration in both directions: ChargerDojo tells the endpoint its credentials are invalid, then invalidates its own. After that the endpoint can no longer reach ChargerDojo, and getting back means issuing a fresh token for them to register with again. Revoke a registered inbound endpoint before removing its row, so its client no longer holds credentials for that registration. The OCPI act is Credentials DELETE in OCPI 2.2.1. Issuing and revoking inbound tokens are app actions, not public API operations.

What counts against your plan

An inbound connection is a connection. Inbound and outbound rows share one ceiling, so three registrations from partners and three endpoints you added are six against the same limit. Revoking does not free the slot on its own, because the row survives holding nothing: remove the row when you are finished with it.

Next

Run a conformance suite against them once the row says registered, or run a charging journey if you want a timed end-to-end flow rather than module-by-module checks.