RCP API (1.0)

Download OpenAPI specification:

RCP services API.

GetRootCertificate

GetRootCertificate

The getRootCert method can be used with the unique ID (UID) of a root certificate in the pool. The UID of each root certificate can be retreived through get all endpoint.

path Parameters
rootCertificateId
required
string

The internal ID of the root certificate in the RCP.

header Parameters
OPNC-from-party-type
string
Enum: "emsp" "cpo" "oem" "pki" "cps" "pcp" "ccp"

Specifies the type of party that originated this request

OPNC-from-party-id
string

Specifies the ID of the party that originated this request. The ID format depends on the type of the party (WMI for OEM, ProviderID for EMSP, OperatorID for CPO, SHA-256 fingerprint of Root CA for PKI or CPS)

OPNC-to-party-type
string
Enum: "emsp" "cpo" "oem" "pki" "cps" "pcp" "ccp"

Specifies the type of party to which this request should be addressed.

OPNC-to-party-id
string

Specifies the party ID to which this request should be addressed. The ID format depends on the type of the party (WMI for OEM, ProviderID for EMSP, OperatorID for CPO, SHA-256 fingerprint of Root CA for PKI or CPS..)

Responses

Response samples

Content type
application/json
{
  • "roootCertificate": {
    }
}

DeleteRootCertificate

DeleteRootCertificate

This method is used by the Ecosystem Operator to delete Root CAs from the Root Certificate Pool. This should not be used by other parties than the Root pool operator to prevent possible wrong usage. Also 2 Factor authorization in the organization shall be considered

A successful delete operation triggers events to all ecosystem users and informs about the deleletion of this Root CA. Existing OEM-Prov Certs or eMSP-Contract Certs which rely on this root CA, might not any more usable.

path Parameters
rootCertificateId
required
string

The internal ID of the root certificate in the RCP.

Responses

GetRootCertificates

GetRootCertificates

Get root certificates from the RCP based on (optional) query input.

query Parameters
pkiType
string (pkiTypeParamV1)
Enum: "emsp" "v2g" "oem" "pe"

Optional parameter to filter for root certificates from V2G, eMSP or OEM PKI.

header Parameters
OPNC-from-party-type
string
Enum: "emsp" "cpo" "oem" "pki" "cps" "pcp" "ccp"

Specifies the type of party that originated this request

OPNC-from-party-id
string

Specifies the ID of the party that originated this request. The ID format depends on the type of the party (WMI for OEM, ProviderID for EMSP, OperatorID for CPO, SHA-256 fingerprint of Root CA for PKI or CPS)

OPNC-to-party-type
string
Enum: "emsp" "cpo" "oem" "pki" "cps" "pcp" "ccp"

Specifies the type of party to which this request should be addressed.

OPNC-to-party-id
string

Specifies the party ID to which this request should be addressed. The ID format depends on the type of the party (WMI for OEM, ProviderID for EMSP, OperatorID for CPO, SHA-256 fingerprint of Root CA for PKI or CPS..)

Responses

Response samples

Content type
application/json
{
  • "rootCertificateCollection": [
    ]
}

PutRootCertificate

Save a root certificate in the RCP.

Expects a Root Certificate Object and the Root Type. This Function should not be called by other parties than the Root Certificate Pool operator to prevent possible wrong usage. Each Root CA in a Plug&Charge Ecosystem must be audited/checked upfront. All parties of the Plug&Charge Ecosystem need to relay on this audits of the different PKI Operators or consumers. A 2 Factor authorization in the organization shall be considered to add a Root CA into the RCP

Request Body schema: application/json

Expects a V2G Root CA and the Root Type

= 1 properties
rootCertificateId
string <uuid> ^[0-9a-fA-F]{8}\-([0-9a-fA-F]{4}\-){3}[0-9a-f...

The UUID of each root certificate is generated by thy system when the root certificate gets registered. It can be used to request an individual certificate using the REST API.

distinguishedName
string^((CN|OU|O|C|DC|ST)=[^,]+,? ?)+$

Reflects the subjects distinguished name field. (informative)

rootCtlList
Array of arrays
Items Enum: "European CTL" "American CTL" "No CTL"

Present the list of the Certificate Trust List (CTL) that recognize the Root CA

rootTypeList
Array of arrays
Items Enum: "eMSP" "V2G" "OEM" "PE"

Present the types linked to the Root CA, e.g. a unique Root certificate could be used as an OEM Root and a eMSP Root

caCertificate
required
string <= 800 characters ^[-A-Za-z0-9+/]+={0,3}$

The root certificate in DER format encoded in Base64.

commonName
string

Reflects the subjects common name value. (informative)

rootAuthorityKeyIdentifier
string

SHA-1 hash of the certificates public key (informative)

rootIssuerSerialNumber
string

serial number in hex format of the certificate (informative)

validFrom
string <date-time>

Reflects the subjects not before date. (infotmative)

validTo
string <date-time>

Reflects the subjects not after date. (infotmative)

organizationName
string

Reflects the subjects organization name value. (informative)

certificateRevocationList
string
crossCertificatePair
string
labeledUri
string

RFC 2079 labeledURI

fingerprint
string

SHA256 certificate fingerprint (informative)

Responses

Request samples

Content type
application/json
{
  • "caCertificate": "MIICUzCCAfmgAwIBAgIQaasA0lm730LOgFKa0wzl7TAKBggqhkjOPQQDAjBVMQswCQYDVQQGEwJERTEVMBMGA1UEChMMSHViamVjdCBHbWJIMRMwEQYKCZImiZPyLGQBGRYDVjJHMRowGAYDVQQDExFWMkcgUm9vdCBDQSBRQSBHMTAgFw0xOTA0MjYwODM3MTVaGA8yMDU5MDQyNjA4MzcxNVowVTELMAkGA1UEBhMCREUxFTATBgNVBAoTDEh1YmplY3QgR21iSDETMBEGCgmSJomT8ixkARkWA1YyRzEaMBgGA1UEAxMRVjJHIFJvb3QgQ0EgUUEgRzEwWTATBgcqhkjOPQIBBggqhkjOPQMBBwNCAAShT8kSNcC+74TND82On2Y2TOf8mYfxw73lKZ7t9cmEXHpMdAgsWBQ4LI+pOMhe6NOHzJbzP38kQTg4zLfw3kU0o4GoMIGlMBMGA1UdJQQMMAoGCCsGAQUFBwMJMA8GA1UdEwEB/wQFMAMBAf8wEQYDVR0OBAoECEtF/4Il/BCWMEUGA1UdIAQ+MDwwOgYMKwYBBAGCxDUBAgEAMCowKAYIKwYBBQUHAgEWHGh0dHBzOi8vd3d3Lmh1YmplY3QuY29tL3BraS8wEwYDVR0jBAwwCoAIS0X/giX8EJYwDgYDVR0PAQH/BAQDAgEGMAoGCCqGSM49BAMCA0gAMEUCIQCq3Qx2BLYVFb7Lt5XXpSlUViYv4cIUOQE1Ce9o2Jyy1QIgZRmVzMVjHZA+toiM000PCUrLppqbLpcRN4MP8kE0OhU="
}