OCPI 2.2.1 API Tester — automatic OCPI 2.2.1 conformance checks for EV charging roaming

OCPI 2.2.1 API Tester calls your CPO or eMSP OCPI endpoint (read-only GET requests), validates the versions list, version details, credentials and the locations, tariffs, sessions, CDRs and tokens modules, and returns a pass, warn or fail row for every check with the exact field path and a sample of the offending object.

What it does

• Handshake - versions, version details, mandatory credentials endpoint, endpoint roles (SENDER or RECEIVER) for your role.
• Envelope - HTTP status, JSON, status_code 1000, timestamp, data, pagination headers.
• Objects - field presence, types, string lengths, enums, ISO 8601 times, coordinates, ISO country codes, CDR totals against charging periods.
• Safe - only GET, SSRF-guarded, redirects re-checked, your token is never echoed.

Who it's for

• CPOs and eMSPs preparing OCPI roaming connections
• Hubs and platform QA teams
• Integrators running a regression check in CI
• Consultants auditing a partner API

Input

Field	Type	Default	Description
mode	string	validate	What to do. validate - test a live OCPI endpoint (empty URL runs a free demo) payload - validate a pasted OCPI response or object offline selftest - health check (for schedules)
versionsUrl	string	``	Public https URL of the OCPI versions endpoint, for example https://cpo.example.com/ocpi/versions. Private and local addresses are blocked. Empty = free demo.
token	string		OCPI token for the Authorization header. It is never written to the output or logs.
tokenEncoding	string	base64	OCPI 2.2.1 sends the token base64 encoded after the word Token. Choose plain only for platforms that skip the encoding.
role	string	CPO	CPO exposes locations, tariffs, sessions and CDRs as sender. eMSP exposes tokens as sender.
modules	array		Which modules to test. Empty = locations, tariffs, sessions, cdrs, tokens, credentials. Allowed: locations, tariffs, sessions, cdrs, tokens, credentials, commands.
depth	string	standard	quick: 3 objects per module. standard: 25. full: 100 objects and the full report fee.
module	string	locations	Module of the pasted JSON in payload mode.
json	object		A pasted OCPI response (with status_code and data), a list of objects or one object.
maxItems	integer	100	Cap on billable rows (module summaries) per run.

Modes: validate, payload, selftest.

Example input

{
  "mode": "validate",
  "versionsUrl": "https://cpo.example.com/ocpi/versions",
  "token": "YOUR_TOKEN",
  "role": "CPO",
  "depth": "standard"
}

Output example

Every row is flat JSON with status (ok, not_found, invalid_input, source_error), source, sourceUrl, fetchedAt and dataAsOf.

{
  "status": "ok",
  "source": "OCPI 2.2.1 specification, checked against the endpoint you provide",
  "sourceUrl": null,
  "fetchedAt": "2026-10-25T08:00:00Z",
  "dataAsOf": null,
  "module": "locations",
  "check": "object #2",
  "result": "fail",
  "detail": "country: 'UA' does not match the required format",
  "sample": "{\"country_code\": \"UA\", ...}"
}

Pricing

Pay per event — you pay only for results, never for empty or failed lookups (not_found, invalid_input and source_error rows are free).

Event	What is charged	Price	Per 1,000
endpointTested	Endpoint tested	$0.02	$20
fullReport	Full report	$0.5	$500

Apify platform usage (compute, storage) is included in the event prices. Set Maximum cost per run in the run options to cap spending; the Actor stops cleanly when the limit is reached. Apify subscribers on Bronze, Silver and Gold plans get automatic discounts on the event prices.

Use with MCP, n8n, Make and Zapier

• Apify MCP server — add https://mcp.apify.com?tools=tiger19935/ocpi-conformance-tester to Claude, Cursor or any MCP client so an AI agent can call this Actor as a tool.
• n8n / Make / Zapier — use the Apify integration, pick Run Actor, select tiger19935/ocpi-conformance-tester and map the dataset items. Saved Tasks + a schedule turn it into a monitor with webhooks.
• API — POST https://api.apify.com/v2/acts/tiger19935~ocpi-conformance-tester/runs or the official Apify clients for JavaScript and Python.

FAQ

Is it legal to use this data? The Actor only reads official open data from the user-supplied OCPI endpoint and the public OCPI 2.2.1 specification. Nothing is stored beyond your run dataset. Every row carries source and sourceUrl so you can attribute it. No captcha, login or personal data of private individuals is bypassed or collected.

How fresh is the data? Each row has dataAsOf - the publication date of the source file or API. If the publisher stops updating, dataAsOf stops moving and the daily self-test run fails, so you can tell stale data from a broken Actor.

What happens when nothing is found or the source is down? You get a not_found or source_error row and you are not charged. The Actor never fails silently with an empty dataset.

How do I get alerts? Create a Task with mode: monitor, schedule it (hourly or daily) and add a webhook, or connect the Apify integration in n8n, Make or Zapier. Only new, changed and removed records are returned and charged.

Does it change anything on my platform? No. Only GET requests are sent. Push (PUT, PATCH) and command (POST) calls are not made.

Is this the official OCPI certification? No. It checks the data model and envelope rules of OCPI 2.2.1 that most integration failures come from. It does not replace the official test tools or a bilateral test.

Why is my local server rejected? Runs happen in the Apify cloud, so private and localhost addresses are blocked. Expose a staging URL or use payload mode with pasted JSON.

Related Actors

• Ukraine Open Data Explorer — browse open datasets