Connected Kerb Charge Point Platform API (AMPECO Public API tenant)

aid: connected-kerb:public-api
name: Connected Kerb Charge Point Platform API (AMPECO Public API tenant)
description: 'Connected Kerb runs its charge point management system on the AMPECO EV charging platform,
  and the platform Public API is live on Connected Kerb''s own host at cp.connectedkerb.com/public-api/.
  Resource endpoints answer with the platform''s JSON authentication envelope and the AMPECO X-App-Version
  header, confirming a genuine server-to-server API instance covering charge points, EVSEs, locations,
  sessions, users, tariffs, partners, circuits and roaming. The contract for this API is published by
  the platform vendor, not by Connected Kerb: there is no Connected Kerb developer portal, no first-party
  OpenAPI, and no public self-service credential issuance. Access is by Bearer API token issued through
  the operator''s back office. Recorded here as an operated surface, not as a Connected Kerb-published
  contract.'
humanURL: https://www.connectedkerb.com/our-technology/software/
baseURL: https://cp.connectedkerb.com/public-api/
tags:
- EV Charging
- Charge Point Management
- Platform API
x-access: gated
x-contract-owner: AMPECO (platform vendor) - contract not published by Connected Kerb
x-platform-docs: https://developers.ampeco.com/
x-platform-openapi: https://developers.ampeco.com/openapi/public-api.yaml
x-evidence:
  fetched: '2026-08-04'
  probes:
  - url: https://cp.connectedkerb.com/public-api/resources/charge-points/v1.0
    http_status: 401
    content_type: application/json
    body: '{"message":"Unauthenticated."}'
    headers:
    - 'X-App-Version: 3.225.1 (9e5dd506)'
  - url: https://cp.connectedkerb.com/public-api/oauth/token
    method: POST
    http_status: 404
    body: '{"message":"Feature is not enabled"}'
    note: OAuth 2.0 client-credentials grant is NOT enabled on this tenant; legacy bearer API tokens only.