Update a card specification or credential values
Credential updates require type credential and the current version, and change only values or description; omitted values are preserved, nonempty strings replace, and null or empty strings clear supported fields. Clearing required text/email/password values returns pending_collection; browser forms still require nonempty required inputs. Card updates may omit type for compatibility with legacy requests. Requested cards accept a replacement specification. Pending issuance requests may update provider-supported fields on their existing request, subject to atomic provider approval checks; omitted optional fields remain unchanged and explicit empty lists clear them. Wallet/provider binding and unsupported fields cannot change after authorization starts. An uncertain update enters recovery_required and must not be retried. Checkout cards may be edited between authorizations.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
- Option 1
- Option 2
Type must match the stored item; an update cannot change item type. Legacy card updates may omit type. Credential updates require explicit type and version. Wallet updates are unsupported.
Response
Vault item updated
- Option 1
- Option 2
- Option 3
Immutable item key assigned when the item is created.
- Option 1
- Option 2
- Option 1
- Option 2
wallet - Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
Live, non-persisted data requested through the item GET expand parameter.