This use case intends to load a peer’s Token from the Backbone by a given reference to the Token.

Parameters

You can execute this use case if you know the truncatedReference of the peer’s Token.

  • reference that identifies the Token.
  • ephemeral to indicate that the Token should be stored locally.
  • The password if the Token is protected by a password via its passwordProtection property.

On Success

  • Returns the corresponding Token.

On Failure

  • The parameters are malformed.
  • The Token does not exist.
  • The Token is expired.
  • The Token is personalized for a different Identity via the property forIdentity of the Token.
  • No password or an incorrect password was entered in case of a password protected Token.

How to execute this use case with the Connector?

The Connector is our first-class citizen, thus we provide you with a detailed API description for every use case. This use case can be executed with the REST API of the Connector which you can Access the Connector.
Corresponding interactive API docs excerpt: