# ChargerDojo - Extended LLM Guide > Test your OCPI endpoint before your first partner does. OCPI 2.1.1, 2.2.1 and 2.3.0. Inspect recorded exchanges and applicable rules, and reasons for checks we could not observe. Sandbox testing, the simulator and the Learning Hub are free with no login. Page-level notes for assembling context. Every public page is listed; the index at [llms.txt](https://chargerdojo.com/llms.txt) is the same set in one line each. ## Agent Access (MCP) ChargerDojo runs a hosted Model Context Protocol server at https://mcp.chargerdojo.com, over Streamable HTTP. Unauthenticated, it answers questions about the OCPI protocol: which versions exist, how each one encodes the credentials token and splits endpoints into sender and receiver interfaces, what changed between two versions, and which modules, suites and charging journeys ChargerDojo can test. Answers come from the same registry the simulator obeys, so they match what the site itself does. Send an `Authorization: Bearer cdojo_…` API key and the same server reads the account behind it: registered endpoints, run history, verdicts, journey events, changes since the previous comparable run, schedules and plan usage. Run details quote recorded clauses and identify rules without one. The server starts conformance runs and charging journeys on endpoints registered on the account. Its access tool names each plan, its price and what it unlocks over MCP. Call `tools/list` for the current tools and their input schemas. This file does not list them, because a copy here would drift from the server. Connect instructions per client: https://docs.chargerdojo.com/guide/connect-a-coding-agent ## OCPI and ChargerDojo Facts Statements below are generated from the registries ChargerDojo itself obeys, so they describe what the product does today rather than what a page once said. Each one is self-contained and safe to quote on its own. ### OCPI versions - ChargerDojo runs OCPI conformance tests against three selectable protocol versions: 2.1.1, 2.2.1 and 2.3.0. - OCPI 2.1.1 sends the credentials token as a raw string in the Authorization header and advertises one endpoint per module, with no SENDER or RECEIVER split. - OCPI 2.2 sends the credentials token base64-encoded in the Authorization header and splits each module into a SENDER interface and a RECEIVER interface. - OCPI 2.2.1 sends the credentials token base64-encoded in the Authorization header and splits each module into a SENDER interface and a RECEIVER interface. - OCPI 2.3.0 sends the credentials token base64-encoded in the Authorization header and splits each module into a SENDER interface and a RECEIVER interface. - ChargerDojo implements OCPI 2.2 but does not offer it as a test target. - ChargerDojo retains OCPI 2.2 for source comparison content, alongside the selectable lesson and test versions OCPI 2.1.1, 2.2.1 and 2.3.0. ### Modules per version - The ChargerDojo OCPI 2.1.1 surface covers 7 modules: cdrs, commands, credentials, locations, sessions, tariffs and tokens. - The ChargerDojo OCPI 2.2 surface covers 9 modules: cdrs, chargingprofiles, commands, credentials, hubclientinfo, locations, sessions, tariffs and tokens. - The ChargerDojo OCPI 2.2.1 surface covers 10 modules: cdrs, chargingprofiles, commands, credentials, hubclientinfo, locations, payments, sessions, tariffs and tokens. - The ChargerDojo OCPI 2.3.0 surface covers 11 modules: booking, cdrs, chargingprofiles, commands, credentials, hubclientinfo, locations, payments, sessions, tariffs and tokens. - The Bookings module of OCPI 2.3.0 and the Direct Payment module of OCPI 2.2.1 are published as standalone EVRoaming Foundation documents rather than inside the core specification, which makes them official OCPI modules that live outside the core chapter list. ### Conformance checks - ChargerDojo runs 54 conformance checks against an OCPI 2.1.1 endpoint. - ChargerDojo runs 157 conformance checks against an OCPI 2.2.1 endpoint. - ChargerDojo runs 172 conformance checks against an OCPI 2.3.0 endpoint. - A ChargerDojo conformance check asserts one rule of the OCPI specification and names the rule it encodes, and where its clause has been read back against the specification text it also quotes that clause. - Scenario walkthroughs are excluded from every ChargerDojo conformance-check count, because a scenario walks a flow from end to end rather than asserting a single clause. - ChargerDojo is not an accreditation body, and a green ChargerDojo run is not an OCPI certification: formal OCPI certification is an EVRoaming Foundation process. ### Why a ChargerDojo verdict can be trusted - ChargerDojo ships four mutant peers, one for each of OCPI 2.1.1, 2.2, 2.2.1 and 2.3.0, and a sweep in which any check a mutation named stays green fails the build. - The ChargerDojo mutant peers carry 255 conformance mutations between them, and each mutation names in advance the checks that must turn red before the build will pass. - A further 88 scenario mutations prove the ChargerDojo charging-journey verdicts the same way, and each of those must redden the check it named in advance. - Every conformance check ChargerDojo runs is either named in advance by a mutation that then reddens it, or listed with a written reason, and the build fails if a check is neither, if a listed reason is blank, or if a mutation starts naming a listed check. - A ChargerDojo mutant peer is a copy of the sandbox with one rule OCPI requires deliberately broken, so a check that stays green against its own mutant is a check that has never been proven capable of failing. - Every ChargerDojo mutation names in advance the check ids that must turn red, and a sweep in which one of them stays green on a graded response fails the build. - Every ChargerDojo conformance check must be reddened by some mutant, and by one that did not redden every check, so a check proven only by a sledgehammer still counts as unproven. ### How a conformance check is graded - A ChargerDojo conformance run sorts every check into exactly one of four outcomes: passed, failed, unobservable, or not applicable. - A ChargerDojo warning is an overlay on the outcome, so warnings are counted separately from passed, failed, unobservable and not-applicable checks. - A passed ChargerDojo check satisfied the requirements inspected by that check. A passed check does not certify the whole endpoint. - A failed ChargerDojo conformance check makes the run not compliant, even when other checks passed. - A ChargerDojo conformance warning records a declined recommendation, either an OCPI SHOULD or one of ChargerDojo's own, and does not itself fail a check. A separate required-rule failure still fails that check. - An unobservable ChargerDojo check graded nothing, either because the response carried nothing to grade or because no request was sent after the partner advertised no such module or interface. - An unobservable ChargerDojo check is never counted as a pass, because counting one as a pass would certify an endpoint that was never examined. ### The OCPI status-code rule - OCPI carries a semantic failure in the response body's status_code field on an HTTP 200 response, and OCPI 2.2, 2.2.1 and 2.3.0 state that an HTTP error status code MUST NOT be returned to a syntactically valid, authenticated request that addresses an existing resource. - OCPI 2.1.1 draws that same boundary as a should rather than a must, so a 2.1.1 partner answering an HTTP error where 2.2.1 forbids one has broken no 2.1.1 clause. - An OCPI server may still answer HTTP 401 for a missing or unknown token, HTTP 404 for a resource that does not exist, and HTTP 405 for a method the module declares not applicable. ### Plans and prices - The ChargerDojo Sandbox plan costs $0, so it is free to use with no login. - The ChargerDojo Integrate plan costs $149 a month, or $1,490 a year. - The ChargerDojo Automate plan costs $499 a month, or $4,990 a year. - The ChargerDojo Custom plan is priced on a quote. - The ChargerDojo Integrate plan includes 3 partner endpoints and the Automate plan includes 20, shared by everyone in the organisation, and the Custom plan sets partner endpoints in its quote. - Running the Direct Payment and Bookings suites against your own endpoint needs the ChargerDojo Automate plan, and against ChargerDojo sandbox endpoints they are free. - Grading a charging journey against Gireve or Plugsurfing Roam behaviour on your own endpoint needs the ChargerDojo Automate plan. - Running a graded charge routed through a hub ChargerDojo plays, against your own endpoint, needs the ChargerDojo Automate plan. - Running the ChargerDojo simulator, the Learning Hub and conformance suites against ChargerDojo sandbox endpoints is free, with no login. - Testing your own OCPI endpoint and CI automation belong to the paid ChargerDojo plans. ### Roaming hub testing - ChargerDojo tests a roaming hub on OCPI 2.2, 2.2.1 and 2.3.0, the versions that define message routing. - ChargerDojo grades 19 roaming hub checks, each backed by an OCPI requirement: 13 by a SHALL, four by a required table row or Response Data definition and two by a lowercase "must" or "have to". It records 11 more in the report without grading them. - On a copy of the ChargerDojo reference hub with one rule broken, the check for that rule must fail; ten of the 19 graded ChargerDojo roaming hub checks are proven this way. - Testing a roaming hub's identity needs the ChargerDojo Integrate plan, $149 a month, and testing its relay and schedules needs the ChargerDojo Automate plan, $499 a month. - ChargerDojo tests a roaming hub by joining it as CPO and eMSP counterparties, sending a Session through it and grading each forward against the OCPI routing rules. - A ChargerDojo roaming hub report is not a certification, and the quoted ChargerDojo Custom plan issues no certificate. - A sample ChargerDojo roaming hub report, run against the ChargerDojo reference hub, is public at https://chargerdojo.com/sample-report/ and free with no login. ### Payment terminal testing - ChargerDojo tests payment terminal integrations on the OCPI 2.2.1 Direct Payment extension and OCPI 2.3.0 Payments. - On OCPI 2.3.0, one ChargerDojo payment terminal run has 13 calls, of which the payment terminal provider's system sends five. - Running ChargerDojo payment terminal testing against the ChargerDojo sandbox is free with no login, and testing your own payment terminal platform needs the ChargerDojo Automate plan, $499 a month. - ChargerDojo plays the CPO against the payment terminal platform. The report names calls the journey expected but did not receive. - When the CPO invoices, ChargerDojo compares the payment terminal provider's captured total with the CDR and reports a mismatch as a warning, and fails a successful capture confirmation that lacks the total, currency or EFT data. - ChargerDojo payment terminal testing covers the OCPI interface of a payment terminal platform, not physical terminals, settlement with a payment processor or AFIR compliance. - ChargerDojo payment terminal checks have run against the ChargerDojo sandbox terminal system, not yet against a payment terminal provider's own system. ### The planned OCPI library - The ChargerDojo OCPI library is a pre-release product in early access: it is planned and not yet built, with no package, published price or release date. - Teams request early access to the ChargerDojo OCPI library at https://chargerdojo.com/product/library/ to choose its first role, programming language and OCPI versions. ### The charging journey catalogue - The ChargerDojo journey manifest defines 24 charging journey templates, one of which is the custom template a hand-authored journey declares. - ChargerDojo groups its charging journeys into 13 packs, one per part of OCPI a journey exercises. - A ChargerDojo charging journey can inject any of 22 disturbances, which are deliberate faults such as a duplicated CDR, a session that never closes, or a transport outage. - A ChargerDojo charging journey drives a timed charge against a real OCPI endpoint, message by message, graded on conformance, business checks and observations. ## Primary Tasks ### Diagnose a roaming interoperability issue Start at the guided scenario matching the symptom: a duplicated charge, a session that never closes, a bill higher than the advertised price, or a refused authorization. Each walks the OCPI messages in order and names the field that decides the outcome. Then open the Explorer page for the module involved to check the object shape, and Version Differences if the two parties run different OCPI versions. ### Onboard a new engineer to OCPI OCPI Explained, then Key Terminologies, then the OCPI Charging Session Lifecycle lesson and the Charging lab. The Knowledge Check shows what stuck. ### Prepare pre-release validation Use the OCPI Testing Tool against your endpoint, and the Payload Workbench for limited 2.2.1 field checks before you send an object. A charging journey covers a whole charge, message by message, rather than a single request. ### Run OCPI conformance programmatically (CI or agent) The Testing API guide is written for unassisted agent use: create a key, start a run with long-poll, read the pass/fail exit contract, and share the report. A sandbox endpoint needs no partner and no credentials. ## Page-Level Notes ### Core Product Pages #### [Test your OCPI endpoint before your first partner does.](https://chargerdojo.com/product/) Connect your own endpoint, behind a firewall too. Use the evidence in your report to fix failures and share the report with your partner. #### [Which page is for your company?](https://chargerdojo.com/solutions/) Each page says which side of the connection we play for you and what a run grades. #### [Protocols we test](https://chargerdojo.com/protocols/) OCPI testing runs today against your own endpoint. OCPP testing is launching soon on the same platform. #### [OCPI versions we test](https://chargerdojo.com/protocols/ocpi/) Test your OCPI endpoint before your first partner does. Pick the version your partner speaks to see the modules its suites check. #### [Home](https://chargerdojo.com/) Test your OCPI endpoint before your first partner does. OCPI 2.1.1, 2.2.1 and 2.3.0. Test against your real endpoint, even one behind a firewall. Send your partner or hub a report with the evidence. #### [OCPI 2.3.0 Testing Scope and Evidence](https://chargerdojo.com/protocols/ocpi/2-3-0/) Check OCPI 2.3.0 module coverage, interface roles and known limitations. Inspect saved report evidence before testing your endpoint with ChargerDojo. #### [OCPI Payment Terminal Testing](https://chargerdojo.com/solutions/payment-terminals/) Test your payment terminal platform's OCPI integration before CPO onboarding. Run the 2.2.1 Direct Payment or 2.3.0 Payments journey free on the sandbox. #### [OCPI Roaming Hub Testing](https://chargerdojo.com/solutions/roaming-hubs/) Test your roaming hub's OCPI routing with CPO and eMSP counterparties. Grade routing headers, request ids, errors and identity on every version that routes. #### [Security and Your Test Data](https://chargerdojo.com/security/) Who can reach your endpoint, how ChargerDojo stores partner tokens and API keys, who can read a report and how long data is kept. Read before you connect. #### [About ChargerDojo](https://chargerdojo.com/about/) Founder Abhishek Uniyal built ChargerDojo so charging just works. It tests your OCPI integration against a counterparty that breaks the rules on purpose. #### [Example OCPI Test Report with Evidence](https://chargerdojo.com/sample-report/) A durable, redacted roaming-hub relay report from ChargerDojo's own reference hub, with its actual capture date, scope, saved exchanges and cited rules. #### [EV Charging Simulator](https://chargerdojo.com/learn/simulator/) Visual message-flow and charging-lifecycle simulation. #### [OCPI Testing Tool](https://chargerdojo.com/product/conformance-testing/) Structured OCPI protocol testing and validation against a real endpoint. #### [OCPP Testing Tool for CSMS and Chargers](https://chargerdojo.com/ocpp-testing/) OCPP, the Open Charge Point Protocol published by the Open Charge Alliance, connects a charger to its charging station management system (CSMS). ChargerDojo OCPP testing is launching soon: OCPP 2.1 and 2.0.1 CSMS testing together, followed by OCPP 1.6J, then charge-point testing. ChargerDojo will play the other side of the connection, drop connections, reboot mid-transaction, omit required fields and quote the governing clause beside each failure. Join the OCPP waitlist. OCPI testing is available today. #### [OCPI Library (pre-release, early access)](https://chargerdojo.com/product/library/) The ChargerDojo OCPI library is a pre-release product: planned and not yet built, with no package, published price or release date. The planned design hands the library a platform's locations, sessions and tokens and has it run the OCPI handshake, module routes and versions. Teams starting an OCPI integration request early access to choose its first role, programming language and OCPI versions. The free MCP payload validator and the Payload Workbench check single OCPI objects today. #### [Plans and Pricing](https://chargerdojo.com/pricing/) The four tiers with monthly and yearly figures, the partner endpoint allowance each paid plan carries, from 3 on Integrate to fair use on a quote, and what the free sandbox covers. A role guide names the plan for each job (CPO, eMSP, payment terminal provider, hub, CI), and a comparison table lists every limit and feature row by row. Custom is a quote rather than a self-serve tier, and it is not a certification: ChargerDojo issues no certificate, and formal OCPI certification happens on the EVRoaming Foundation test tool, EVRTT. #### [Charging journeys](https://chargerdojo.com/product/charging-journeys/) Timed OCPI charges against a real endpoint, message by message, with disturbances and separate graded verdicts for conformance, business checks and observations. ### Hub Integration Preparation #### [OCPI Hub Integration Testing Preparation](https://chargerdojo.com/integrations/) Find roaming issues while your team can still fix them. Test the OCPI endpoint, inspect the evidence and take a clear report into onboarding. #### [Gireve OCPI Testing and Onboarding Preparation](https://chargerdojo.com/integrations/gireve-ocpi-testing/) Find protocol mistakes in your own environment before partner testing starts. Run OCPI suites and charging journeys, then take the evidence into Gireve onboarding. #### [Hubject OCPI Testing Preparation](https://chargerdojo.com/integrations/hubject-ocpi-testing/) Build confidence in the OCPI side before onboarding. Test your own endpoint and bring a report with the exchanges your run recorded. ### Learn OCPI #### [Learning Hub](https://chargerdojo.com/learn/) Learning path overview and related modules. #### [OCPI Explained](https://chargerdojo.com/learn/ocpi-explained/) OCPI fundamentals, roles, and protocol model. #### [Key Terminologies](https://chargerdojo.com/learn/key-terminologies/) Practical glossary for implementation and support. #### [OCPI Charging Session Lifecycle](https://chargerdojo.com/learn/charging-session/) Step-by-step session phases from authorization to CDR. #### [Knowledge Quiz](https://chargerdojo.com/learn/quiz/) Assessment-oriented checkpoint for team alignment. #### [Version Differences](https://chargerdojo.com/learn/versions/) What changed across OCPI 2.1.1, 2.2.1 and 2.3.0: new modules, SENDER/RECEIVER roles, token encoding, and field additions. ### Guided Scenarios Step-by-step OCPI workflow walkthroughs with message-level sequencing, the best pages for "how does X work in OCPI" and "why did this go wrong" questions. #### [Scenarios Overview](https://chargerdojo.com/learn/scenarios/) All guided scenarios with difficulty and scope. #### [Complete EV charging session](https://chargerdojo.com/learn/scenarios/charging-session/) Follow an authored charging session from the driver arriving at the charger through energy delivery and billing between participating roaming platforms. #### [One card, two countries](https://chargerdojo.com/learn/scenarios/cross-border-charge/) A driver with a German contract charges at a Dutch operator's charger. The CPO and the eMSP are in different countries, and each object names the country and party that owns it. #### [Remote start and stop](https://chargerdojo.com/learn/scenarios/remote-start-stop/) An eMSP remotely starts and stops an authored charging session on behalf of a driver, using OCPI's asynchronous command exchange. #### [Roaming connection setup](https://chargerdojo.com/learn/scenarios/roaming-registration/) How a CPO and eMSP discover each other, exchange credentials, and synchronize locations and tokens to enable roaming. #### [Charged twice for one charge](https://chargerdojo.com/learn/scenarios/charged-twice/) In this authored billing example, a dropped connection leads to a fresh CDR ID and two customer charges. A Credit CDR illustrates correction of a sent record. #### [Tariff and billing](https://chargerdojo.com/learn/scenarios/tariff-billing/) How pricing flows from tariff publication through to the final invoice. Covers the full billing lifecycle from CPO pricing to driver payment. #### [The authorization that says no](https://chargerdojo.com/learn/scenarios/token-not-allowed/) A driver taps an expired card and the charge is refused. The lesson is what a refusal actually looks like on the wire: a successful exchange carrying a 'no', not an error. #### [The bill was higher than the price I saw](https://chargerdojo.com/learn/scenarios/bill-higher-than-shown/) A driver sees a daytime energy rate before a time-of-day tariff changes. This authored example follows the difference between the displayed rate and the customer bill. #### [The Session that never closes](https://chargerdojo.com/learn/scenarios/session-never-closes/) A charge starts and meters normally, then the eMSP does not receive its closing update. Follow the missing-message observation and the reconciliation it needs. ### OCPI Module Reference (Explorer) Interactive per-module reference covering endpoints, payloads, and behaviours, grounded in the published specification text for each version. #### [Explorer Overview](https://chargerdojo.com/learn/explorer/) All OCPI modules at a glance, with the version each was introduced in. #### [Sessions](https://chargerdojo.com/learn/explorer/sessions/) OCPI Sessions share a charging record between platforms. Read the versioned fields, lifecycle and interface methods, then inspect an illustrative request. #### [CDRs](https://chargerdojo.com/learn/explorer/cdrs/) OCPI CDRs share the record used for billing between platforms. Read the fields, delivery rules and interface methods for the selected OCPI version. #### [Locations](https://chargerdojo.com/learn/explorer/locations/) OCPI Locations describe charging sites, EVSEs and connectors. Read their versioned fields, update methods and source clauses with illustrative endpoint paths. #### [Tariffs](https://chargerdojo.com/learn/explorer/tariffs/) OCPI Tariffs describe charging prices between platforms. Compare the selected version's fields and interface methods with examples and source clauses. #### [Tokens](https://chargerdojo.com/learn/explorer/tokens/) OCPI Tokens identify drivers for charging authorization. Read versioned fields, synchronization and real-time authorization interfaces with source clauses. #### [Commands](https://chargerdojo.com/learn/explorer/commands/) OCPI Commands request actions such as remote start and stop. Read the versioned replies and asynchronous callback interfaces with source clauses. #### [Credentials](https://chargerdojo.com/learn/explorer/credentials/) OCPI Credentials register platforms and exchange access tokens. Read the selected version's identity fields, registration methods and source clauses. #### [Versions](https://chargerdojo.com/learn/explorer/versions/) OCPI version discovery lists supported versions and their module URLs. Compare the selected version's endpoint fields and interface definitions. #### [Hub Client Info](https://chargerdojo.com/learn/explorer/hubclientinfo/) OCPI Hub Client Info shares connected-party status through a hub. Check version availability, fields and interface methods with the relevant source clauses. #### [Charging Profiles](https://chargerdojo.com/learn/explorer/chargingprofiles/) OCPI Charging Profiles request charging limits for a Session. Check version availability, asynchronous replies and interface methods with source clauses. #### [Payments](https://chargerdojo.com/learn/explorer/payments/) OCPI Payments connects charging operators and payment terminal providers. Compare the Direct Payment extension and core module with versioned sources. #### [Bookings](https://chargerdojo.com/learn/explorer/booking/) OCPI Bookings is a separately published extension. Check version availability and read its Booking, BookingLocation and Calendar interfaces with sources. ### Lesson and scenario steps Each step of a lesson or scenario at its own address, opening with its direct answer and, where it makes a protocol claim, the verbatim clause it cites. #### [What is OCPI?](https://chargerdojo.com/learn/ocpi-explained/introduction/) OCPI, the Open Charge Point Interface, connects charging platforms. Participating networks exchange charging information to support roaming. #### [Why OCPI matters](https://chargerdojo.com/learn/ocpi-explained/purpose/) OCPI connects charging platforms for roaming. They exchange locations, prices, authorization and charging records used for billing. #### [Key players in OCPI](https://chargerdojo.com/learn/ocpi-explained/key-entities/) A Charging Point Operator operates charge points; an e-Mobility Service Provider gives drivers access to charging. #### [How OCPI works](https://chargerdojo.com/learn/ocpi-explained/how-it-works/) An OCPI exchange has a request and a response. Platforms discover module URLs, then exchange charging data under their selected version. #### [OCPI roles knowledge check](https://chargerdojo.com/learn/ocpi-explained/knowledge-check/) This OCPI knowledge check asks you to identify the parties and the purpose of roaming. #### [Where to go after the OCPI primer](https://chargerdojo.com/learn/ocpi-explained/summary/) The OCPI primer introduces the platforms, their roles and the exchanges between them. #### [Meet the two parties](https://chargerdojo.com/learn/charging-session/meeting-the-players/) An OCPI charging exchange connects a charging network operator with a driver service provider. #### [Starting a charging session](https://chargerdojo.com/learn/charging-session/starting-a-session/) The CPO authorizes the driver's token, in real time with the eMSP or from its own copy of the eMSP's tokens, then pushes the new Session to the eMSP. #### [Real-time updates during charging](https://chargerdojo.com/learn/charging-session/real-time-updates/) OCPI Session updates carry changes from the charging network operator to the driver service provider. #### [Send a Session update](https://chargerdojo.com/learn/charging-session/2.1.1/session-update/) In OCPI 2.1.1 the CPO sends every change to a Session it already pushed by calling PATCH on the eMSP's Sessions endpoint. #### [Send a Session update](https://chargerdojo.com/learn/charging-session/2.2.1/session-update/) In OCPI 2.2.1 and 2.3.0 the CPO sends every change to a Session it already pushed by calling PATCH on the eMSP's Sessions endpoint. #### [Finishing the charging session](https://chargerdojo.com/learn/charging-session/finishing-a-session/) Finishing an OCPI Session means sending its final state to the driver service provider. #### [Order the charging session messages](https://chargerdojo.com/learn/charging-session/building-your-first-flow/) This authored OCPI flow follows one card-started charging session. Order the messages between the CPO and eMSP, then compare the record held by each platform. #### [Authorize the driver](https://chargerdojo.com/learn/charging-session/authorization/) Token authorization asks whether a driver identification record may be used to charge. #### [Start the Session](https://chargerdojo.com/learn/charging-session/start-session/) An OCPI Session is the charging record the CPO shares with the eMSP. In this local example the driver plugs in, then the CPO creates and pushes the record. #### [Charge and update the Session](https://chargerdojo.com/learn/charging-session/charging/) A Session update carries changes to the charging record. This local example adds simulated energy readings and illustrates a CPO update to the eMSP. #### [Stop the Session](https://chargerdojo.com/learn/charging-session/stop-session/) The final OCPI Session update records completion of the charging session. In this local example the driver stops and the CPO updates the shared record. #### [Send the CDR](https://chargerdojo.com/learn/charging-session/billing-cdr/) An OCPI charge detail record, or CDR, describes a charge for billing. This local example shows the CPO sending it to the eMSP after the Session completes. #### [Driver taps an RFID card on the charger](https://chargerdojo.com/learn/scenarios/charging-session/driver-arrives/) The driver arrives at the charging station and taps their RFID card on the charger to identify themselves. #### [Charger asks the CPO about the token](https://chargerdojo.com/learn/scenarios/charging-session/charger-auth-request/) The charger doesn't recognize the token locally. It forwards the authorization request to the CPO's backend system to check if this driver can charge. #### [CPO asks the eMSP to authorize the token](https://chargerdojo.com/learn/scenarios/charging-session/token-authorization/) The CPO asks the eMSP to authorize a driver Token. Read how whitelist values guide the choice between local authorization and a real-time request. #### [Authorization succeeds and charging begins](https://chargerdojo.com/learn/scenarios/charging-session/charger-unlocks/) Authorization succeeded. The CPO tells the charger to unlock the connector. The driver plugs in the cable and charging begins. #### [CPO pushes the new Session to the eMSP](https://chargerdojo.com/learn/scenarios/charging-session/session-start/) The charger begins delivering energy. The CPO creates a session record and pushes it to the eMSP so the driver can see charging progress in their app. #### [CPO sends Session updates with meter values](https://chargerdojo.com/learn/scenarios/charging-session/meter-values/) The charger reports new meter readings. The CPO updates the session with current energy delivered and sends the update to the eMSP. The CPO owns the Session. #### [Driver unplugs and the final reading arrives](https://chargerdojo.com/learn/scenarios/charging-session/driver-unplugs/) The driver returns to their car and unplugs the cable. The charger detects the disconnection and reports the final meter reading to the CPO. #### [CPO pushes the COMPLETED Session](https://chargerdojo.com/learn/scenarios/charging-session/session-stop/) The CPO marks the session as COMPLETED with the total energy delivered and final cost, then pushes the update to the eMSP. The CPO owns the Session. #### [CPO sends the CDR for billing](https://chargerdojo.com/learn/scenarios/charging-session/cdr-creation/) The CPO creates the billing-relevant CDR after the charge and sends it to the eMSP. The excerpt shows cost and charging-period information. #### [eMSP accepts the CDR and bills the driver](https://chargerdojo.com/learn/scenarios/charging-session/driver-billed/) The eMSP accepts the CDR and bills the driver in this authored example. Separate the OCPI billing record from the receipt shown in the driver app. #### [Start the charging lab](https://chargerdojo.com/learn/scenarios/charging-session/tutorial-intro/) The OCPI charging lab follows one authored Session. Inspect messages between the CPO and eMSP, then configure a separate simulated network. #### [Set up the OCPI simulator](https://chargerdojo.com/learn/scenarios/charging-session/simulator-basics/) The OCPI simulator models CPO, eMSP and charger actors. Configure a network in Free exploration; the guided charge keeps its authored actors. #### [Simulate a charging session](https://chargerdojo.com/learn/scenarios/charging-session/session-simulation/) An OCPI charging flow connects authorization, Session updates and the CDR. Follow the guided example or inspect your simulated network. #### [Explore the OCPI messages](https://chargerdojo.com/learn/scenarios/charging-session/message-exploration/) An OCPI message has a sender, a receiver and an endpoint. Inspect the request and read the HTTP status separately from the response body. #### [Choose your next step](https://chargerdojo.com/learn/scenarios/charging-session/completion/) The OCPI charging lab connects a Session to its authorization, updates and CDR. Revisit a message or try a field puzzle before another scenario. #### [Version discovery agrees on an OCPI version](https://chargerdojo.com/learn/scenarios/roaming-registration/version-discovery/) The eMSP reads the CPO versions list and discovers the module endpoints for its selected OCPI version. Follow the registration example and its sources. #### [CPO and eMSP exchange credentials](https://chargerdojo.com/learn/scenarios/roaming-registration/credentials-exchange/) Still using token A, the eMSP POSTs CREDENTIALS_TOKEN_B to the credentials endpoint it found in the version details. #### [CPO pushes its Locations to the eMSP](https://chargerdojo.com/learn/scenarios/roaming-registration/location-sync/) The CPO shares charging locations with the eMSP after registration. Read the illustrative Location exchange and the selected OCPI version sources. #### [eMSP pushes its Tokens to the CPO](https://chargerdojo.com/learn/scenarios/roaming-registration/token-sync/) The eMSP shares driver Tokens with the CPO after registration. Read how whitelist values govern authorization when the platforms cannot communicate. #### [eMSP sends a StartSession command](https://chargerdojo.com/learn/scenarios/remote-start-stop/start-command/) The eMSP asks the CPO to start charging with START_SESSION. Read the authored request, its asynchronous reply and the sources for the selected OCPI version. #### [CPO posts the start command result](https://chargerdojo.com/learn/scenarios/remote-start-stop/command-response/) The CPO posts the result of a remote start command. Read why initial acceptance and a callback do not prove that charging started in this OCPI example. #### [CPO pushes the remotely started Session](https://chargerdojo.com/learn/scenarios/remote-start-stop/session-created/) Session creation uses PUT to share the new charging record with the eMSP. A command acceptance alone does not prove that charging started. #### [eMSP sends a StopSession command](https://chargerdojo.com/learn/scenarios/remote-start-stop/stop-command/) The driver taps Stop in the app. The eMSP sends a STOP_SESSION command naming the Session it received, SESSION-R001, and a new response_url. #### [CPO posts the stop command result](https://chargerdojo.com/learn/scenarios/remote-start-stop/step-5-stop-callback/) The CPO posts a CommandResult to the stop command's response_url. Its ACCEPTED means the charger accepted the stop request. #### [CPO completes the remotely stopped Session](https://chargerdojo.com/learn/scenarios/remote-start-stop/step-6-session-completed/) The CPO sends the final Session update with PATCH: status COMPLETED, the energy delivered and the end time. #### [CPO publishes its Tariff to the eMSP](https://chargerdojo.com/learn/scenarios/tariff-billing/tariff-publication/) The CPO publishes its tariff structure to the eMSP. This tariff defines the price per kWh, any time-based fees, and optional parking charges. #### [CPO updates the running Session cost](https://chargerdojo.com/learn/scenarios/tariff-billing/session-with-tariff/) The CPO updates the running Session cost in this authored example. Read how charging periods and tariff restrictions relate to the selected OCPI version. #### [CPO sends a CDR with its cost breakdown](https://chargerdojo.com/learn/scenarios/tariff-billing/cdr-with-cost/) The CPO sends a CDR after charging ends. Read the energy, parking time, tariff details and total cost shown in this version of the billing example. #### [eMSP prepares the driver's invoice](https://chargerdojo.com/learn/scenarios/tariff-billing/invoice-generation/) In this authored example, the eMSP's billing system uses the captured CDR data to prepare the driver's invoice. #### [CPO publishes a time-of-day Tariff](https://chargerdojo.com/learn/scenarios/bill-higher-than-shown/publish-tariff/) The CPO publishes its tariff to the eMSP. It has a time-of-day step: 0.35 per kWh before 17:00, and 0.55 per kWh after. Tariffs describe CPO prices. #### [Driver sees the rate in force at 16:40](https://chargerdojo.com/learn/scenarios/bill-higher-than-shown/driver-sees-price/) At 16:40 the driver plugs in. Their app shows 0.35 per kWh, the rate that is in force right now. That is the number they will remember. #### [CDR bills each period at its own rate](https://chargerdojo.com/learn/scenarios/bill-higher-than-shown/cdr-produced/) The driver charges from 16:40 to 17:30 local time. The Location's time_zone is Europe/Amsterdam, so the tariff's 17:00 is 16:00 UTC on this February day. #### [Driver disputes the higher bill](https://chargerdojo.com/learn/scenarios/bill-higher-than-shown/driver-billed/) The eMSP charges the driver 17.90. The driver, who saw 0.35 per kWh, disputes the difference. #### [CPO POSTs the CDR and the eMSP stores it](https://chargerdojo.com/learn/scenarios/charged-twice/cdr-sent/) A charge finishes. The CPO, NL-FPN, sends CDR CDR-NL-GCH-88401 for Session session-7710 to the eMSP, which stores it. #### [A retry creates a second CDR ID](https://chargerdojo.com/learn/scenarios/charged-twice/retry-duplicates/) A dropped answer leads to a new CDR ID and a second customer charge in this authored example. Read the correction rules for your OCPI version. #### [Driver arrives at a charger abroad](https://chargerdojo.com/learn/scenarios/cross-border-charge/arrive-abroad/) A driver uses a German provider's card at a Dutch charger. Follow the CPO and eMSP exchange, with identity fields explained for each OCPI version. #### [Dutch CPO asks the German eMSP to authorize](https://chargerdojo.com/learn/scenarios/cross-border-charge/real-time-authorize/) The token's whitelist value is NEVER, so the Dutch CPO asks the token's owner, the German eMSP, to authorize it in real time, naming the location. #### [CPO pushes the Session to the home eMSP](https://chargerdojo.com/learn/scenarios/cross-border-charge/session-opens/) Power starts flowing. The Dutch CPO opens Session session-9920 under its own country and party, NL and FPN, and pushes it to the German eMSP. #### [Home eMSP bills the CDR from abroad](https://chargerdojo.com/learn/scenarios/cross-border-charge/cdr-settles/) The CPO sends the billing record to the eMSP in this authored example. Compare its Token and location references across OCPI versions. #### [CPO opens and pushes the Session](https://chargerdojo.com/learn/scenarios/session-never-closes/session-start/) The driver plugs in and charging begins. The CPO opens Session session-4471 and pushes it to the eMSP, so the driver's app can show charging. #### [CPO sends a PATCH with the energy so far](https://chargerdojo.com/learn/scenarios/session-never-closes/metering/) As power flows, the CPO sends a PATCH with the energy delivered so far and a new last_updated. The eMSP's copy is ACTIVE at 18.4 kWh. #### [Charger loses its connection at unplug](https://chargerdojo.com/learn/scenarios/session-never-closes/driver-unplugs/) The driver unplugs, but the charger loses its connection in this authored example. Follow what the CPO and eMSP can observe before investigating. #### [No closing Session update or CDR arrives](https://chargerdojo.com/learn/scenarios/session-never-closes/close-never-arrives/) The eMSP receives no closing Session update or CDR in this authored example. Read the last observed state and separate a missing message from a refusal. #### [Driver taps a card with a lapsed contract](https://chargerdojo.com/learn/scenarios/token-not-allowed/card-tap/) A driver holds their card to the charger to start charging. The card is real, but the contract behind it lapsed last month. #### [CPO requests real-time authorization](https://chargerdojo.com/learn/scenarios/token-not-allowed/real-time-authorize/) The token's whitelist value is NEVER, so the CPO asks the eMSP to authorize it in real time, naming the location and EVSE the driver wants to use. #### [Charger refuses to start charging](https://chargerdojo.com/learn/scenarios/token-not-allowed/charge-refused/) The CPO tells the charger the token may not charge. The charger shows 'Not authorized', delivers no energy, and no session is ever created. ### Optional #### [Privacy Policy](https://chargerdojo.com/privacy-policy/) Data handling and rights information. #### [Refund & Cancellation Policy](https://chargerdojo.com/refund-policy/) Billing, cancellation, and refund terms. #### [Terms of Service](https://chargerdojo.com/terms-of-service/) Service terms, what a conformance result means, and acceptable use. ## Documentation Site - [Testing API guide](https://docs.chargerdojo.com/api): Run OCPI conformance suites programmatically: API-key auth, run start with long-poll, pass/fail exit contract, shareable report links, and a copy-paste CI recipe. - [Try a sandbox test in the browser](https://docs.chargerdojo.com/guide/browser-quickstart): A free first report without an API key, scoped to ChargerDojo's sandbox peer. - [What ChargerDojo tests](https://docs.chargerdojo.com/guide/coverage): Versions, interfaces, extensions, sandbox limits and what a report proves. - [What this is, and what it will not do](https://docs.chargerdojo.com/guide/index): Scope and limits stated up front. Not certification; a declined SHOULD is never a failure. - [Plans and pricing](https://docs.chargerdojo.com/guide/plans): What is free at every tier, why the API key needs a plan, and what Integrate, Automate and Custom cost and unlock. - [Quickstart](https://docs.chargerdojo.com/guide/quickstart): A green run against a sandbox endpoint from the command line. Needs an API key, which needs a paid plan; the run itself is free. - [Glossary](https://docs.chargerdojo.com/guide/glossary): Every OCPI and ChargerDojo term these guides use, in a sentence each: CPO, eMSP, CDR, Token A/B/C, sender and receiver, scenario, unobservable. - [Connect a coding agent](https://docs.chargerdojo.com/guide/connect-a-coding-agent): Point Claude Code, Codex, Cursor or another MCP client at the hosted ChargerDojo server to answer OCPI questions and read your test runs. - [Test a private endpoint](https://docs.chargerdojo.com/guide/connect-a-local-endpoint): Choose a local connector or public tunnel, register the private endpoint and stop access after testing. - [Let a partner register with you](https://docs.chargerdojo.com/guide/let-a-partner-register): The inbound direction: issue a registration token, let their client drive the handshake, and read the row states while you wait. - [Author a custom journey](https://docs.chargerdojo.com/guide/author-a-scenario): The custom journey JSON shape, the knobs that matter, and how to import, run and save a journey written by hand or generated from CI. - [Test a payment terminal](https://docs.chargerdojo.com/guide/test-a-payment-terminal): Register your payment terminal platform as a PTP with the payments module advertised, run the Direct terminal payment journey on OCPI 2.2.1 or 2.3.0, and read the report. - [Test a roaming hub](https://docs.chargerdojo.com/guide/test-a-roaming-hub): Register with your own OCPI hub as one CPO party to check its identity, or as a CPO and eMSP pair to trace a Session and its error response through it, with a reference hub sample report. - [Connect a partner endpoint](https://docs.chargerdojo.com/guide/connect-a-partner): Creating a connection. Token A comes from the partner, out of band. - [Create an API key](https://docs.chargerdojo.com/guide/create-an-api-key): Keys are created and revoked in the app; the plaintext shows once. - [Run a conformance suite](https://docs.chargerdojo.com/guide/run-a-suite): Starting runs, `?wait=` (200 finished vs 202 still running), and a CI recipe that separates "they broke a rule" from "we got no answer". - [Verdicts, counts and run states](https://docs.chargerdojo.com/guide/verdicts): The five verdicts; conformance and journey counters, run states and missing evidence. - [Read your report](https://docs.chargerdojo.com/guide/read-your-report): Find the first failed exchange, read its applicable rule, fix the endpoint and retest. - [Check a payload](https://docs.chargerdojo.com/guide/check-a-payload): Edit and compare OCPI payloads in your browser, with limited field checks for 2.2.1. Nothing you paste leaves the page. Free, no login. - [Share a report](https://docs.chargerdojo.com/guide/share-a-report): Public read-only report links for a partner. No auth needed to read one. - [Work with a colleague](https://docs.chargerdojo.com/guide/work-with-a-colleague): Invite someone into your organisation, what each role may do, that partner endpoints are shared rather than per person, and what happens to their work when they leave. - [Run a charging journey](https://docs.chargerdojo.com/guide/run-a-charging-journey): Timed charges against your endpoint with graded verdicts, idempotent starts, and honest recovery states. - [Troubleshoot](https://docs.chargerdojo.com/guide/troubleshooting): The failures that actually happen: public status codes, and how a target failure differs from our service status. - [Changelog](https://docs.chargerdojo.com/changelog): Which rules changed how they grade, and when to run a test again because an old report failed you. ## Implementation and Crawl References - [Sitemap](https://chargerdojo.com/sitemap.xml): Canonical list of indexable public pages. - [Robots](https://chargerdojo.com/robots.txt): Crawl directives and blocked internal paths.