Activate Custody Provider
Makes a saved provider the one that serves custody. Exactly one provider is active at a time: activating one deactivates all the others, so there is no separate deactivate call.
The provider must have been saved with Upsert Custody Provider first. Activation does not test the connection; run Test Custody Connection before switching. The server that answers picks up the change immediately; other platform processes pick it up within their refresh window (30 seconds by default).
Platform owner only. The caller's node must be the platform root node; any other caller is refused with 403 / 10005.
Required permission: custodial-wallet:update
Request
POST /v2/admin/custodial-wallets/{provider}/activate
Parameters
| Name | Type | In | Description |
|---|---|---|---|
provider | string | path | Required. Provider key: rudiq or taurus |
Headers
| Name | Description |
|---|---|
Authorization | Required. Bearer <access_token> |
Example
curl --request POST \
--url '{{baseUrl}}/v2/admin/custodial-wallets/rudiq/activate' \
--header 'Authorization: Bearer <access_token>'
Response
204 No Content with an empty body.
Errors
| Status | Code | Description |
|---|---|---|
| 400 | 10015 | Unsupported provider key |
| 400 | 10000 | The provider has never been saved (message: custodial wallet setting not found). Note that the other providers have already been deactivated when this is returned |
| 403 | 10005 | The caller is not the platform owner (domain 2) |
See Errors for the error format and common codes.