Create Multiple Subaddresses

Endpoint Description: `/user-addrs/multichain`

This endpoint is designed to facilitate the creation of multiple new blockchain addresses across different chains based on the specified requirements. It allows the batch creation of addresses, enhancing efficiency for operations that need to manage multiple wallet addresses simultaneously.

Request Body Requirements

Array of Objects: Each object in the array must specify the blockchain chain, the count of addresses to generate, and optionally, the type of address, which is relevant for certain chains.

Properties

chain: Specifies the blockchain type for which the address(es) will be generated. Supported values are 'BITCOIN', 'ETHEREUM', 'LITECOIN', 'TRON', 'ARBITRUM_ONE' and 'OPTIMISM'.

count: Indicates the number of addresses to generate. The value must be an integer between 1 and 10.

type (optional): Specifies the type of address to generate. For BITCOIN, the valid types are DEFAULT and P2WPKH. For all other chains, the only valid type is DEFAULT. This field defaults to DEFAULT if not provided.

Validation Rules

Chain Specific:

For BITCOIN, both DEFAULT (which generates a P2TR type address) and P2WPKH are valid values for the type field.

For chains other than BITCOIN, the type must be DEFAULT.

Type Constraints:

The type field is validated based on the chain specified:

If BITCOIN is selected, type can be either DEFAULT or P2WPKH.

For ETHEREUM and OPTIMISM, only DEFAULT is acceptable.

Count Validation:

The count must be a positive integer and should not exceed 10 to prevent excessive load and potential misuse of the service.

Error Handling

Custom error messages are provided to ensure that any input validation errors are clearly communicated to the developer, aiding in quick resolution:

Chain Validation Error: "Invalid chain specified. Allowed chains are 'BITCOIN', 'ETHEREUM', 'LITECOIN', 'TRON', 'ARBITRUM_ONE' and 'OPTIMISM'.

Rate Limit

Specified rate limit for this endpoint is 3 requests per IP address per minute.

Request

Authorization

Add parameter in header

apikey

Example:

apikey: ********************

Body Params application/json

array of:

chain

enum<string>

required

Allowed values:

BITCOINETHEREUMOPTIMISMLITECOINARBITRUM_ONETRON

count

integer

required

>= 1<= 6

type

enum<string>

optional

Allowed values:

DEFAULTP2WPKH

Example

[
    {
      "chain": "ETHEREUM",
      "count": 1
    },
    {
    "chain": "BITCOIN",
    "count": 1,
    "type": "P2WPKH"
    },
    {
      "chain": "TRON",
      "count": 1
    },
    {
    "chain": "ARBITRUM_ONE",
    "count": 1
    },
    {
      "chain": "OPTIMISM",
      "count": 1
    },
    {
    "chain": "LITECOIN",
    "count": 1
    }
]

Request samples

Shell

JavaScript

Java

Swift

PHP

Python

HTTP

Objective-C

Ruby

OCaml

Dart

Create Multiple Subaddresses

Endpoint Description: /user-addrs/multichain#

Request Body Requirements#

Properties#

Validation Rules#

Error Handling#

Rate Limit#