Claim non-custodial control for a customer
Initiates a multi-signer non-custodial provisioning flow. Returns 202 with a claimId; per-signer verification URLs are delivered via wallet_signer.invited webhooks.
Valid roster shapes depend on the customer’s signing mode, which Conduit sets per organization (with an optional per-customer override) — confirm the customer’s configured mode before building the roster: passkey required — any api_key member returns 422 SIGNING_MODE_ROSTER_INVALID; programmatic — api_key members must have role: "signer" (an api_key admin returns 422 SIGNING_MODE_ROSTER_INVALID); programmatic unattended — api_key admins are allowed. In every mode the active signers of any credential type must be able to reach signingThreshold; passkeys count toward it. Each api_key member carries a publicKey — the compressed public key, 33 bytes / 66 hex chars, 02/03 prefix, on the curve of its signatureScheme (p256 by default, or secp256k1 / secp256k1_eip191) — and is seated active at claim — an all-machine roster activates the wallets without an enrollment phase; mixed rosters wait on every passkey enrollment. Omitting chains provisions the default set: base, ethereum, polygon, tron. A chain whose addresses need a one-time on-chain account setup is refused with 422 NON_CUSTODIAL_CHAIN_NOT_SUPPORTED. See Programmatic payout signing and Add a crypto wallet.
Authorizations
Headers
Caller-generated unique key that lets the server safely replay this request. The original response is returned for 30 days on any retry with the same key from the same organization. Required on every state-changing money-moving or resource-creating POST.
1 - 128^[A-Za-z0-9_.:-]{1,128}$"01J7B3K2X9M8N5P6Q7R8S9T0V1"
Path Parameters
"cus_1A2b3C4d5E6f7G8h9I0jKl"
Body
Everyone who will be able to approve on this wallet. At least 2 members, of whom at least 2 must be admins. Each member activates their own signer afterwards.
2 - 100 elementsHow many roster members must approve before a transaction is signed. At least 1, and never more than the roster size.
1 <= x <= 9007199254740991Optional. Chains to provision (each must be a supported chain). Omit to auto-provision the default chain set (recommended) so later chain use needs no re-authentication. Accepting a chain here does not imply Conduit operationally supports asset movement on it yet.
1 - 100 elementsethereum, base, solana, polygon, tron, stellar Response
Id of this claim, carried by the webhooks that report its progress. Each id has the form wcc_ followed by 22 alphanumeric characters.
^wcc_[0-9A-Za-z]{22}$Customer the wallets are provisioned for. Each id has the form cus_ followed by 22 alphanumeric characters.
^cus_[0-9A-Za-z]{22}$Always provisioning: the claim was accepted and the wallets are being set up in the background. Wait for the wallet_signer.* and crypto_wallet.completed webhooks.
provisioning How many signers the claim put on the roster.
0 <= x <= 9007199254740991How many signer stamps each payout needs to proceed. Separate from activation, which waits for every roster member to enroll.
0 < x <= 9007199254740991Advisory estimate of minutes to full activation (not an SLA).
-9007199254740991 <= x <= 9007199254740991