Post Roaming-Agreement Actions

Once both partners have agreed to an offer and the roaming agreement is signed, ENAPI enables the exchange of OCPI data between them. While data exchange is now active, there are some actions partners should take to ensure smooth operations.

What needs to happen?

Immediately after an agreement is signed, your partner's data is available to you. For drivers to successfully start charging, please do the following.

If you are a CPO: Pull RFID tokens of your new eMSP partner from ENAPI to support authorization logic and request routing.*

If you are an eMSP: Pull your new CPO partner's Tariffs and Locations from ENAPI to display accurate POI information to your users.

Note:* Not all eMSPs share tokens in advance — some rely on start commands for authorization instead. If this is the case, token pulls will not return any data for that partner. See the ENAPI Data Quality overview to check what data to expect from each of your roaming partners.

Alternatively, if your implementation does not support pulling data, ENAPI can push the relevant data (tokens, tariffs, and locations) directly to your backend when a new agreement is activated. Please reach out to help@enapi.com if you'd like to use this approach.

Can I automate this process?

OCPI 2.2.1

On 2.2.1, ENAPI can notify your backend of new operators via a PUT on the HubClientInfo module or a handshake refresh, if supported. Partners could use these notifications as a trigger to automatically start a full pull.

OCPI 2.1.1

Given that OCPI 2.1.1 does not support the HubClientInfo module and indeed the hub topology, options here are more limited. Therefore, we encourage partners' commercial and technical teams to work closely together to coordinate the pulls manually.

How can I learn more?

If you have any questions about how to handle these steps in your specific implementation, reach out to help@enapi.com — we're happy to help.