<p>You do not use the single key pair data to create an extended public key. The single address you generated with the API is not relevant in this situation.  The HD Wallet Endpoint is a feature where you can provide your own extended public key from an external wallet (not blockcyphers).</p>
<p>Related question/answer on extended public keys: <a href="https://bitcoin.stackexchange.com/questions/74246/how-to-generate-a-new-extended-public-key-xpub">How to generate a new extended public key (xpub)?</a></p>

CC BY-SA 4.0
2022-01-28T05:10:30.653Z
2022-01-28T05:10:30.653Z
m1xolyd1an
<p>I'm using Blockcypher to <a href="https://www.blockcypher.com/dev/bitcoin/#create-wallet-endpoint" rel="nofollow noreferrer">create an HD wallet</a>, which requires me to send <code>extended_public_key</code>.</p>
<p>How do I create the extended keys?
While generating a new address using <a href="https://www.blockcypher.com/dev/bitcoin/#generate-asset-address-endpoint" rel="nofollow noreferrer">the API</a> I'm getting something like:</p>
<pre><code>{
  &quot;private&quot;: &quot;696785dc619c5f493ba72aa1ded581771ac7360fcf49903a0dc96a381d460182&quot;,
  &quot;public&quot;: &quot;03d6ff03e21b81a7f5c7e678130845a94ba1ca15316bc0d9635c8cc3e51aa26a8a&quot;,
  &quot;address&quot;: &quot;bc1q446jd78q2nmpxt25puv7h8lwcwsw9dmkgf5sgp&quot;,
  &quot;wif&quot;: &quot;KzkbwXy4PS8mEAnZZC5LcVnhe64LCWaqUfsc4Fuj1AKak4qgBPcJ&quot;
}
</code></pre>
<p>How can I use this data to create extended private and public keys?</p>
<p>Should I use a different method to generate the extended keys?</p>

<private-key><bip32-hd-wallets><public-key><blockcypher>
Creating HD wallet using Blockcypher
forhas
# Creating HD wallet using Blockcypher

(Asked by: username_0 on 2022-01-26)

I'm using Blockcypher to [create an HD wallet](https://www.blockcypher.com/dev/bitcoin/#create-wallet-endpoint), which requires me to send `extended_public_key`.

How do I create the extended keys?
While generating a new address using [the API](https://www.blockcypher.com/dev/bitcoin/#generate-asset-address-endpoint) I'm getting something like:

```
{
  "private": "696785dc619c5f493ba72aa1ded581771ac7360fcf49903a0dc96a381d460182",
  "public": "03d6ff03e21b81a7f5c7e678130845a94ba1ca15316bc0d9635c8cc3e51aa26a8a",
  "address": "bc1q446jd78q2nmpxt25puv7h8lwcwsw9dmkgf5sgp",
  "wif": "KzkbwXy4PS8mEAnZZC5LcVnhe64LCWaqUfsc4Fuj1AKak4qgBPcJ"
}

```

How can I use this data to create extended private and public keys?

Should I use a different method to generate the extended keys?

**Tags:** private-key, bip32-hd-wallets, public-key, blockcypher


---

## 1 answers

### Answer by username_1 on 2022-01-28. Score: 0 | Accepted answer

You do not use the single key pair data to create an extended public key. The single address you generated with the API is not relevant in this situation. The HD Wallet Endpoint is a feature where you can provide your own extended public key from an external wallet (not blockcyphers).

Related question/answer on extended public keys: [How to generate a new extended public key (xpub)?](https://bitcoin.stackexchange.com/questions/74246/how-to-generate-a-new-extended-public-key-xpub)


---

