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 returns401. 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.