WalletD developers
Catalog

The merchant's API keys, without secrets

The merchant's API keys with their environment, scopes, status and last use.

GET/v1/clients/{clientId}/api_keys

The merchant's API keys with their environment, scopes, status and last use. Secrets are never included; a key's token exists only in the response that issued it. Only a person may manage keys, so a key — bound or not — is refused consumer_token_required (403); the caller must also have authority over the client (not_client_member or insufficient_scope, 403). A deployment without merchant keys configured answers merchant_keys_disabled (501).

Authorization

bearerAuth
AuthorizationBearer <token>

A tenant API key (sk_{env}_{id}_{secret}), a wallet user token, or an IdP access token. Which principal the credential resolves to decides the scopes it carries; see the authentication guide.

In: header

Path Parameters

clientId*string
Formatuuid

Response Body

application/json

application/problem+json

application/problem+json

application/problem+json

curl -X GET "https://example.com/v1/clients/497f6eca-6276-4993-bfeb-53cbbbba6f08/api_keys"
[  {    "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",    "env": "sandbox",    "name": "string",    "scopes": [      "string"    ],    "status": "active",    "created_at": "2019-08-24T14:15:22Z",    "expires_at": "2019-08-24T14:15:22Z",    "last_used_at": "2019-08-24T14:15:22Z"  }]