> For the complete documentation index, see [llms.txt](https://docs.enapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enapi.com/getting-started/the-enapi-portal.md). # The ENAPI Portal The ENAPI portal is where you manage the full lifecycle of a roaming relationship — from finding partners and signing agreements, through monitoring OCPI data flows, to validating CDRs and settling invoices. The sidebar follows that lifecycle. Each section corresponds to a stage. ### Roaming — commercial relationships Where roaming relationships start. You'll use this section most during partnership setup. * **Partners.** Browse every CPO and eMSP on the ENAPI network. The table shows role, EVSE count (CPO only), active countries, and current roaming status with you. Click **Make offer** to initiate a new partnership directly from here. * **Legal Contracts.** Your active roaming agreements and their terms. * **Offers.** Manage roaming offers — sent and received. Click **New offer** to send one to any partner. ### Technical — data flowing through the connection Once an agreement is live, OCPI data starts moving. This section is your visibility layer. * **Locations.** Charging station data — your own (as a CPO) or your partners' (as an eMSP). * **Sessions.** Live and historical charging sessions across all your roaming connections. * **Data Quality.** Your data health dashboard: OCPI object counts per partner, sync freshness, and flagged issues. ### CDRs — the billing records Every completed session produces a Charge Detail Record. This is where you review them. * **Inbox.** As a CPO, the CDRs you've sent to partners. As an eMSP, the CDRs you've received. ENAPI automatically runs your configured validation checks and flags anomalies. * **Configuration.** Define the validation rules ENAPI applies to your CDRs. See [Validation Rules Reference](/cdr-clearing/validation-rules-reference.md). ### Financial — money moves Where CDRs become invoices and invoices become payments. What appears here depends on your role. * **Bill Pay (eMSPs).** Reconcile partner invoices against the CDR data ENAPI has on record. Currently in pilot — reach out to join. ### Settings & Support At the bottom of the sidebar. * **Settings.** Profile, organization, technical handshakes, legal entities, and more. See [Settings and Configuration](/getting-started/settings-and-configuration.md). * **Support.** Access the Help Center or reach the ENAPI team via Slack or email. ### What you see depends on your role Your role on ENAPI is set during the OCPI handshake, based on what you declare in your credentials. ENAPI infers whether you're a CPO, eMSP, or dual-role partner — and that determines what appears in the portal. In OCPI terms: CPOs push locations, tariffs, and CDRs; eMSPs push tokens and consume location and session data. Dual-role partners run both, usually under separate party IDs to keep data flows clean. The sidebar is the same for both roles. What you see inside each section, and which sections appear at all, depends on whether you're a CPO or an eMSP. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.enapi.com/getting-started/the-enapi-portal.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.