aid: enapi
name: Enapi
description: >-
  Enapi (ENAPI) operates a unified roaming and clearing platform for the electric
  vehicle charging industry, brokering transactions between Charge Point Operators
  (CPOs) and e-Mobility Service Providers (eMSPs). Rather than exposing a proprietary
  API, Enapi implements the open OCPI (Open Charge Point Interface) standard
  out-of-the-box across versions 2.1.1, 2.2.1, and 2.3.0, operating as an OCPI HUB
  that handles version interoperability, message routing, and endpoint fan-out on
  behalf of partners. Its three product lines are Roaming (peer-to-peer commercial
  connections while Enapi handles the technical integration), Technical (standardized
  OCPI onboarding with automated testing and a staging environment), and Financial
  CDR Clearing (real-time Charge Detail Record validation, dispute flagging, and
  settlement). As of early 2024 the platform connects over 700,000 charge points and
  works with most major eMSPs including partners such as TotalEnergies, ChargePoint,
  ubitricity, Plugsurfing, Monta, and Eneco.
url: https://raw.githubusercontent.com/api-evangelist/enapi/refs/heads/main/apis.yml
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://enapi.com/media/pages/home/6908c67d54-1749641656/enapi_blue_inverse-web-1000x.png
x-type: company
x-source: vc-portfolio
x-backed-by:
- seedcamp
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- EV Charging
- OCPI
- Roaming
- E-Mobility
- Charge Point Operator
- eMSP
- Electric Vehicle
- CDR Clearing
- Interoperability
- Hub
apis:
- name: Enapi OCPI Roaming API
  description: >-
    Enapi's OCPI HUB endpoint for EV charging roaming. Implements the Open Charge
    Point Interface (OCPI) 2.1.1 / 2.2.1 / 2.3.0 across the Credentials, Locations,
    Tariffs, Tokens, Sessions, CDRs, Commands, HubClientInfo, and Payments modules.
    Authentication is via OCPI token exchange (handshake) with tokens carried in the
    Authorization header (Base64-encoded for 2.2.1+).
  humanURL: https://docs.enapi.com/technical-documentation
  baseURL: https://roaming.enapi.com
  properties:
  - type: Documentation
    url: https://docs.enapi.com
  - type: Authentication
    url: authentication/enapi-authentication.yml
  - type: Sandbox
    url: sandbox/enapi-sandbox.yml
common:
- type: Website
  url: https://enapi.com
- type: DeveloperPortal
  url: https://docs.enapi.com
- type: Documentation
  url: https://docs.enapi.com
- type: APIReference
  url: https://docs.enapi.com/technical-documentation
- type: GettingStarted
  url: https://docs.enapi.com/getting-started
- type: Login
  url: https://app.enapi.com/login
- type: SignUp
  url: https://calendly.com/enapi/let-s-talk
- type: Support
  url: https://docs.enapi.com/security-compliance-and-slas/incident-management
- type: StatusPage
  url: https://status.enapi.com/
- type: TermsOfService
  url: https://enapi.com/terms-of-use
- type: PrivacyPolicy
  url: https://enapi.com/privacy-policy
- type: Compliance
  url: https://docs.enapi.com/security-compliance-and-slas/compliance-and-data-residency
- type: LLMsTxt
  url: llms/enapi-llms.txt
- type: Authentication
  url: authentication/enapi-authentication.yml
- type: Conventions
  url: conventions/enapi-conventions.yml
- type: Conformance
  url: conformance/enapi-conformance.yml
- type: Lifecycle
  url: lifecycle/enapi-lifecycle.yml
- type: Sandbox
  url: sandbox/enapi-sandbox.yml
- type: DomainSecurity
  url: security/enapi-domain-security.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence