Welcome to our new developer portal! Use the "Ask" button to chat with our AI Agent.

Register

Register APIs.

Register consumer

put
/issuers/{issuerId}/consumers/{consumerId}

This request is used by the issuer backend to request the registration of the end user (consumer). As an input only the consumerId and the state are needed.

Authorizations
AuthorizationstringRequired

A JWT generated by the Get Authorization Token API.
The server checks the validity of the provided token to control access to this protected resource. Please refer to Get OAuth 2.0 access token for more details on the flow and on how to get this JWT.

Path parameters
issuerIdstring · min: 10 · max: 10Required

The id of the issuer

consumerIdstring · min: 1 · max: 64Required

Unique identifier of the end user.

Pattern: [A-Za-z0-9_-]{1,64}
Header parameters
x-correlation-idstring · min: 1 · max: 64Optional

Random identifier which can be used to correlate the different API calls done as part of a single use-case. This identifier will be the one primarily used for troubleshooting.

Warning: This identifier should not be derived from sensitive personal data, as its value will be logged in clear.

There is no strong guarantee of the uniqueness of this identifier, so please refrain from using it for purposes other than logging and troubleshooting.

Pattern: [a-zA-Z0-9_\-\. ]{1,64}
Body

The following object represent the consumer

statestring · enumOptionalDeprecated

The state of the end user (consumer)
Note: Consumer state is deprecated, Thales will no more check the consumer's state. You can still pass it but it will be ignored.

Possible values:
Responses
204

Successful end user registration

No content

put
/issuers/{issuerId}/consumers/{consumerId}

No content

Register consumer with cards

put
/issuers/{issuerId}/consumers/{consumerId}/cards

This request is used by the issuer backend to register an end user (consumer) with his associated set of cards. The cards must be already created on the Issuer CMS side. This allows D1 to make this end user (consumer) and his or her cards eligible to other D1 services like tokenisation, secure card display, push porvisioning... If not provided in this API (in the encryptedData parameter), D1 manages to retrieve useful card information from the issuer backend based on the cardId provided by calling get card credentials API.

Authorizations
AuthorizationstringRequired

A JWT generated by the Get Authorization Token API.
The server checks the validity of the provided token to control access to this protected resource. Please refer to Get OAuth 2.0 access token for more details on the flow and on how to get this JWT.

Path parameters
issuerIdstring · min: 10 · max: 10Required

The id of the issuer

consumerIdstring · min: 1 · max: 64Required

Unique identifier of the end user.

Pattern: [A-Za-z0-9_-]{1,64}
Header parameters
x-correlation-idstring · min: 1 · max: 64Optional

Random identifier which can be used to correlate the different API calls done as part of a single use-case. This identifier will be the one primarily used for troubleshooting.

Warning: This identifier should not be derived from sensitive personal data, as its value will be logged in clear.

There is no strong guarantee of the uniqueness of this identifier, so please refrain from using it for purposes other than logging and troubleshooting.

Pattern: [a-zA-Z0-9_\-\. ]{1,64}
Body
Responses
204

Successful end user (consumer) & cards registration

No content

put
/issuers/{issuerId}/consumers/{consumerId}/cards

No content

Last updated

Was this helpful?