Jump to
Ctrl
+
/

Derive And Sync New Change Addresses

POST
/blockchain-data/{blockchain}/{network}/hd/derive-sync-change

Through this endpoint users can derive 100 change addresses, starting from the last index we have data for, which are then added to the xPub, subscribed for syncing, and start recording data. If no data is available, it will start from index 0. We use type P2WPKH.

Path Parameters

blockchain string Required

Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.

network string Required

Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - "mainnet" is the live network with actual data while network like "testnet" is a test network.

Query Parameters

context string Optional

In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.

Request Body Schema application/json

context string Optional

In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.

data object Required
item object Required
extendedPublicKey string Required

Defines the account extended publicly known key which is used to derive all child public keys.

Response Schema

apiVersion string Required

Specifies the version of the API that incorporates this endpoint.

2021-03-20
requestId string Required

Defines the ID of the request. The requestId is generated by Crypto APIs and it's unique for every request.

601c1710034ed6d407996b30
context string Optional

In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.

yourExampleString
data object Required
limit integer Required

Defines how many items should be returned in the response per page basis.

50
offset integer Required

The starting index of the response items, i.e. where the response should start listing the returned items.

0
total integer Required

Defines the total number of items returned in the response.

100
items array Items (object) Required
address string Required

Represents the public address, which is a compressed and shortened form of a public key.

tb1q2sy5l2vn4p648g3ttjxegghp6w9nycvdxap4ef
addressFormat string Required

Represents the format of the address.

P2WPKH
addressType string Required

Defines the address type.

change
derivationType string Required

Represents the derivation type.

bip32
index string Required

Represents the output index. It refers to the UTXO sequence in the transaction outputs (vout).

1

Credits Cost : 10000 Credits for 1 Results

Was this page helpful?
Yes
No
Language
URL

{
    "apiVersion": "2021-03-20",
    "requestId": "601c1710034ed6d407996b30",
    "context": "yourExampleString",
    "data": {
        "limit": 50,
        "offset": 0,
        "total": 100,
        "items": [
            {
                "address": "tb1q2sy5l2vn4p648g3ttjxegghp6w9nycvdxap4ef",
                "addressFormat": "P2WPKH",
                "addressType": "change",
                "derivationType": "bip32",
                "index": "1"
            }
        ]
    }
}