Credentials
Credentials in OCPI 2.2.1
The Credentials module registers two platforms and exchanges their access details. Authenticate this illustrative POST with bootstrap Token A. Its body supplies a different token for requests back to the registering platform.
Sources (2)
Example request · registration-post
Authorization: Token ZXhhbXBsZS1ib290c3RyYXAtQQ==
{
"token": "example-reverse-B",
"url": "https://sender.example.invalid/versions",
"roles": [
{
"role": "CPO",
"party_id": "EXA",
"country_code": "NL",
"business_details": {
"name": "Example Sender"
}
},
{
"role": "EMSP",
"party_id": "EXA",
"country_code": "NL",
"business_details": {
"name": "Example Provider"
}
}
]
}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.
Both parties
Retrieves the credentials object to access the server's platform.
GET/ocpi/ 2.2.1/ credentials/ Provides the server with a credentials object to access the client's system (i.e. register).
POST/ocpi/ 2.2.1/ credentials/ Provides the server with an updated credentials object to access the client's system.
PUT/ocpi/ 2.2.1/ credentials/ Informs the server that its credentials to the client's system are now invalid (i.e. unregister).
DELETE/ocpi/ 2.2.1/ credentials/
Source
Try an endpoint
Send a request to this site's OCPI endpoints and read the answer. It never reaches your own system.