postWalletWithHttpInfo method

Future<Response> postWalletWithHttpInfo(
  1. CreateWalletIn createWalletIn
)

Provisions a new signing identity under one of the caller org's accounts and answers the stored wallet including its on-chain address.

Provisions a new signing identity under one of the caller org's accounts and answers the stored wallet including its on-chain address. The custody backend generates the key material — a KMS-sealed secp256k1 key, an MPC threshold key on the ring, or a Safe smart wallet owned by one — and the HANDLE to it is kept server-side and never returned. A custody kind the deployment has not wired fails CLOSED with 503: a signature is never fabricated. The wallet is scoped to the org, the caller's ambient project, and optionally an agent and the named account; those narrowings are what its key ref is derived from, so each must be a url-safe segment.

Note: This method returns the HTTP Response.

Parameters:

Implementation

Future<Response> postWalletWithHttpInfo(CreateWalletIn createWalletIn,) async {
  // ignore: prefer_const_declarations
  final path = r'/v1/wallet';

  // ignore: prefer_final_locals
  Object? postBody = createWalletIn;

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

  const contentTypes = <String>['application/json'];


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