# OCPI 2.2.1 API Tester: CPO and eMSP Endpoint Validation (`tiger19935/ocpi-conformance-tester`) Actor

OCPI 2.2.1 API tester and validator for EV charging roaming. Point it at a CPO or eMSP versions URL and get a pass, warn or fail report for versions, credentials, locations, tariffs, sessions, CDRs and tokens. Paste-JSON mode for offline checks. Pay per endpoint tested.

- **URL**: https://apify.com/tiger19935/ocpi-conformance-tester.md
- **Developed by:** [Andrew Boiko](https://apify.com/tiger19935) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $16.00 / 1,000 endpoint testeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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

```json
{
  "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`.

```json
{
  "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](https://apify.com/tiger19935/ukraine-open-data-explorer) — browse open datasets

# Actor input Schema

## `mode` (type: `string`):

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` (type: `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` (type: `string`):

OCPI token for the Authorization header. It is never written to the output or logs.

## `tokenEncoding` (type: `string`):

OCPI 2.2.1 sends the token base64 encoded after the word Token. Choose plain only for platforms that skip the encoding.

## `role` (type: `string`):

CPO exposes locations, tariffs, sessions and CDRs as sender. eMSP exposes tokens as sender.

## `modules` (type: `array`):

Which modules to test. Empty = locations, tariffs, sessions, cdrs, tokens, credentials. Allowed: locations, tariffs, sessions, cdrs, tokens, credentials, commands.

## `depth` (type: `string`):

quick: 3 objects per module. standard: 25. full: 100 objects and the full report fee.

## `module` (type: `string`):

Module of the pasted JSON in payload mode.

## `json` (type: `object`):

A pasted OCPI response (with status_code and data), a list of objects or one object.

## `maxItems` (type: `integer`):

Cap on billable rows (module summaries) per run.

## Actor input object example

```json
{
  "mode": "validate",
  "versionsUrl": "",
  "tokenEncoding": "base64",
  "role": "CPO",
  "depth": "standard",
  "module": "locations",
  "maxItems": 100
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `table` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "versionsUrl": ""
};

// Run the Actor and wait for it to finish
const run = await client.actor("tiger19935/ocpi-conformance-tester").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "versionsUrl": "" }

# Run the Actor and wait for it to finish
run = client.actor("tiger19935/ocpi-conformance-tester").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "versionsUrl": ""
}' |
apify call tiger19935/ocpi-conformance-tester --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,tiger19935/ocpi-conformance-tester"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/MTGVg9j4aQ5OpsaE0/builds/oal5IYeaEH75lt2LQ/openapi.json