Multisig Wallets
Add a treasury contact
Name a destination so the treasury can transfer to it. Reserved to a signer holding an active key here: naming an address is the durable trust decision, where a transfer is only a proposal that the signature threshold still gates. The address is stored lowercase, and a mixed-case input has its EIP-55 checksum verified — a hand-retyped address fails it. It cannot be changed afterwards: archive the contact and add a new one, which is what puts "never used" back in front of the signers.
post/v1/multisig-wallets/{walletId}/contacts
Request
- Base URL: https://api.prod.keyban.io
- URL: https://api.prod.keyban.io/v1/multisig-wallets/{walletId}/contacts
- Auth: one of:
- API key in header X-Api-Key
- bearer (a scheme the document does not define)
Path parameters
walletIdstring uuid required
The unique identifier of the multisig wallet
Request body
Example request
{
"label": "Prestataire Acme",
"address": "0xcb0c0dca4246bb0f6b3309d64e7e35002cc3af1f"
}Response
Contact added
Example response
{
"label": "Prestataire Acme",
"address": "0xcb0c0dca4246bb0f6b3309d64e7e35002cc3af1f"
}Changes
No recorded changes to this operation across all 1 revision of this API.