> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/guardian/standard-registry/fireblocks-raw-signing/getting-keys-from-fireblocks-ui.md).

# Getting Keys from FireBlocks UI

1. Create API user by clicking on Developer Center option in the side menu and then clicking on Add API User:

<figure><img src="/files/n5ICLcayT3OQeiEWwM3o" alt=""><figcaption></figcaption></figure>

In new API user dialog, you can download Private key file or upload your custom key file.

<figure><img src="/files/gIoiOHQ8d2WdrHdFwnen" alt=""><figcaption></figcaption></figure>

Content of this file you need to pass into “Fireblocks Private Key” field.

2. When the user was created – click on Settings and then click on the Key icon for the respective user to copy API Key:

<figure><img src="/files/qVG2DFlxOM5R5Xlsn9px" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/tDYpjKg0V6Lm4AV5rz5c" alt=""><figcaption></figcaption></figure>

Use this to fill the “Fireblocks API key” field.

3. In the FireBlocks console navigate to the “Accounts” tab and select one of the accounts listed. Create a wallet for HBAR (mainnet) or HBAR\_TEST (testnet) asset ID. Click on the wallet created, the number in url should be used for the value in the “Fireblocks Vault ID” field, and the asset name chosen is for the “Fireblocks Asset ID” field.

<figure><img src="/files/zZARgGh9t5cUDI0M2VFx" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/91w35Or97KrwaG8pABGV" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/hZtNAKAwJwWj5IPzTEH4" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/HUQ6NwIO5QXET0QPrWsp" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guardian.hedera.com/guardian/standard-registry/fireblocks-raw-signing/getting-keys-from-fireblocks-ui.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.