postWalletByIdKeysWithHttpInfo method

Future<Response> postWalletByIdKeysWithHttpInfo(String id)

Rolls one wallet's signing material through its own custody backend and answers the wallet with whatever address that produced.

Rolls one wallet's signing material through its own custody backend and answers the wallet with whatever address that produced. For KMS custody a fresh secp256k1 key is generated and sealed, which CHANGES the address — funds and approvals at the old address do not move. For a Safe the address is counterfactual and the owner shares are ring-managed, so rotation is a no-op and the address is unchanged. A backend that is not configured fails closed with 503 rather than leaving the wallet half-rotated.

Note: This method returns the HTTP Response.

Parameters:

• String id (required):

Implementation

Future<Response> postWalletByIdKeysWithHttpInfo(String id,) async {
  // ignore: prefer_const_declarations
  final path = r'/v1/wallet/{id}/keys'
    .replaceAll('{id}', id);

  // ignore: prefer_final_locals
  Object? postBody;

  final queryParams = <QueryParam>[];
  final headerParams = <String, String>{};
  final formParams = <String, String>{};

  const contentTypes = <String>[];


  return apiClient.invokeAPI(
    path,
    'POST',
    queryParams,
    postBody,
    headerParams,
    formParams,
    contentTypes.isEmpty ? null : contentTypes.first,
  );
}