For the complete documentation index, see llms.txt. This page is also available as Markdown.

Technical Documentation

Technical reference for the teams implementing against ENAPI. Getting Started and Roaming got you connected and roaming. This section is what your engineers will come back to.

Implement OCPI once

Every OCPI implementation in production is slightly different — different versions, different module coverage, different interpretations of optional fields. Without a clearing layer, you absorb that variance into your code for every new partner.

ENAPI handles it. Your team implements OCPI once, against ENAPI. We translate between versions, normalize field interpretations, and shield you from partner-specific quirks. This section documents what we support and how we behave.

In this section

Start with the page that matches your question:

Last updated

Was this helpful?