generated: '2026-07-27' method: probed source: >- Live probes of https://char.gy/open-ocpi/*, https://char.gy/ocpi/cpo/* and the char.gy help centre, 2026-07-27 versioning: open_feed: scheme: none detail: >- No version is declared anywhere on the open data feed. GET /open-ocpi/versions returns 404, so the OCPI version-negotiation mechanism is not implemented, and the payload shape is the only contract. There is no version in the path, no version header and no media-type versioning. cpo_roaming: scheme: uri-path supported: ['2.2.1', '2.1.1'] rejected: ['2.2'] evidence: >- /ocpi/cpo/2.2.1/locations and /ocpi/cpo/2.1.1/locations return HTTP 401 (real, credential-gated routes) while /ocpi/cpo/2.2/credentials returns status_code 3002 "Unsupported version" — so version support is directly observable without a credential. versions_endpoint: https://char.gy/ocpi/cpo/versions versions_endpoint_status: 401 deprecation: policy_url: null policy_published: false sunset_header: false detail: >- No deprecation policy, no RFC 8594 Sunset or Deprecation header, and no notice period is published for either surface. No Deprecation pointer is wired in apis.yml because none exists. deprecated_operations: [] status_page: url: null published: false detail: >- status.char.gy does not resolve and https://char.gy/status returns 404. No uptime or incident-history page was found, so no StatusPage pointer is wired. Per-charge-point availability is, however, effectively self-reporting through the EVSE status field on /open-ocpi/locations, which regulation 10(4) requires to be updated within 30 seconds of a change. sla: url: null uptime_target: null detail: >- No SLA is published for either API. The statutory obligation in regulation 10 is on data availability, not on API uptime, and char.gy makes no availability commitment to data consumers. changelog: url: null published: false detail: >- No changelog, release notes or version history exists for either surface. The only published documentation is one Freshdesk article with no version and no date. Data freshness must be inferred from last_updated on each object and from the date_from/date_to filters. freshness_observed: locations_total: 5409 updated_since_2026_07_27: 2396 oldest_sampled: >- Only 6 locations had last_updated before 2026-07-01, indicating the whole feed is actively rewritten rather than stale. tariffs_note: >- Of three tariff objects, the EUR and USD records were last_updated in October 2025 while the GBP record was updated 2026-07-23. support: channel: support@char.gy help_center: https://help.char.gy/