Versions
Versions in OCPI 2.2.1
The Versions module tells a platform which OCPI versions and module URLs its partner offers. Follow the supplied Versions URL and the Version.url returned for the negotiated version. This first object is one Version entry; the second is VersionDetails. Request Locations at its advertised Endpoint.url, not a path guessed from the protocol version. Optional modules that were not advertised are not prerequisites. Endpoint.role names SENDER or RECEIVER interfaces, not market roles. The Credentials role value has no function and can be disregarded.
Sources (8)
Example payload · version-entry
{
"version": "2.2.1",
"url": "https://peer.example.invalid/discovery/release-info"
}Example payload · version-details
{
"version": "2.2.1",
"endpoints": [
{
"identifier": "credentials",
"url": "https://peer.example.invalid/access/registration",
"role": "SENDER"
},
{
"identifier": "locations",
"url": "https://peer.example.invalid/charge-sites",
"role": "SENDER"
}
]
}Which endpoints does this module define?
These paths illustrate the requests. Use the URLs advertised by your partner, replace the placeholders and choose the matching interface. A listed method does not establish that this site's simulator implements it.
All parties
Discover supported versions.
GET/ocpi/ versions
Source
All parties
Discover module URLs for a version.
GET/ocpi/ 2.2.1/
Source
Try an endpoint
Send a request to this site's OCPI endpoints and read the answer. It never reaches your own system.