GET
Get secure key
The first call in the secure-details flow. Returns a secretKey (use it to decrypt the secure card data) and a cipher (pass it back when you fetch the data). Next, get a secure card details passkey challenge.

Authorizations

Authorization
string
header
required

The user's id_token from authentication — the ID token, not the access_token. The program and environment come from the token.

Path Parameters

customerId
string
required

The customer's id.

accountId
string
required

The account the card belongs to. A customer can have several accounts; cards are issued against one.

Response

Session key + cipher

success
boolean
Example:

true

data
object