Endpoint structure

How the MOBI.Hub discovers participants' endpoints and builds the final URL for each module.

MOBI.Hub exposes its OCPI interfaces through dedicated endpoints. The reference endpoints for the MOBI.Hub platform are:

• Quality: https://hub-qld.mobie.pt/ocpi/hub/versions
• Production: https://hub.mobie.pt/ocpi/hub/versions

MOBI.Hub does not impose any restrictions regarding the hostname, domain name or base path used by CPOs and EMSPs to expose their OCPI services.

In particular, the endpoints exposed for the Versions, Version Details and Credentials modules may follow any structure chosen by the participant.

Dynamic discovery

The discovery of all OCPI endpoints is performed dynamically through the standard Versions and Credentials procedures.

Once the Version Details endpoint has been retrieved, MOBI.Hub uses the URLs advertised for each module and role to construct the final endpoint according to the rules defined by the OCPI specification.

For example, if a participant exposes the following Sessions receiver endpoint:

• https://api.example.com/custom/path/sessions

MOBI.Hub will construct the URL for updating a session according to the OCPI specification:

{sessions_endpoint_url}/{country_code}/{party_id}/{session_id}

• Example: https://api.example.com/custom/path/sessions/PT/ABC/123456

The same principle applies to all OCPI modules that define additional path parameters.