How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

fireblocks Whitelisted External Wallets API

The Whitelisted External Wallets API from fireblocks — 4 operation(s) for whitelisted external wallets.

fireblocks Whitelisted External Wallets API is one of 35 APIs that Fireblocks publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Whitelisted External Wallets. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a JSON-LD context.

This API exposes 8 operations across 4 paths, and defines 21 schemas. It is described by OpenAPI 3.2.0, at version 1.8.0.

Requests are made against 2 base URLs: https://api.fireblocks.io/v1, https://sandbox-api.fireblocks.io/v1.

8 operations 4 paths 21 schemas 2 DELETE3 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.8.0
Base URL
https://api.fireblocks.io/v1
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

fireblocks Whitelisted External Wallets API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerTokenAuth). An API key is passed in the header as X-API-Key (ApiKeyAuth).

Paths & Operations 8

Across 4 paths, the API surfaces 8 operations — 2 DELETE, 3 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Whitelisted External Wallets 8
GET
/external_wallets
List external wallets
getExternalWallets → 200default
POST
/external_wallets
Create an external wallet
createExternalWallet 1 param body → 200default
GET
/external_wallets/{walletId}
Find an external wallet
getExternalWallet 1 param → 200default
DELETE
/external_wallets/{walletId}
Delete an external wallet
deleteExternalWallet 1 param → 201default
POST
/external_wallets/{walletId}/set_customer_ref_id
Set an AML customer reference ID for an external wallet
setExternalWalletCustomerRefId 2 params body → 201default
GET
/external_wallets/{walletId}/{assetId}
Get an asset from an external wallet
getExternalWalletAsset 2 params → 200default
POST
/external_wallets/{walletId}/{assetId}
Add an asset to an external wallet.
addAssetToExternalWallet 3 params body → 200default
DELETE
/external_wallets/{walletId}/{assetId}
Delete an asset from an external wallet
removeAssetFromExternalWallet 2 params → 201default

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are WalletAssetAdditionalInfo (16 properties), UsWirePaymentInfo (15 properties), SepaPaymentInfo (14 properties), AbaPaymentInfo (11 properties). Each schema is shown below with its type and property counts.

CreateWalletRequest
object
2 properties
WalletAssetAdditionalInfo
object
16 properties
AddAssetToExternalWalletRequest
BasicAddressRequest
object
Basic external wallet request with address information
2 properties 1 required
MomoPaymentInfo
object
Mobile Money (MOMO) payment information for African mobile payment services
9 properties 7 required
WalletAsset
object
7 properties
AdditionalInfoRequest
object
External wallet request with additional payment information for various payment rails
1 property 1 required
PixPaymentInfo
object
PIX payment information for Brazilian instant payments
9 properties 7 required
ConfigChangeRequestStatus
string
AbaPaymentInfo
object
ABA payment information for US bank transfers
11 properties 8 required
UnmanagedWallet
object
4 properties 3 required
SpeiBasicPaymentInfo
object
Basic SPEI payment information for Mexican bank transfers
2 properties 1 required
AchPaymentInfo
object
ACH payment information for US Automated Clearing House transfers
8 properties 8 required
LbtPaymentInfo
object
LBT (Lebanese Bank Transfer) payment information for Lebanese bank transfers
8 properties 8 required
SepaPaymentInfo
object
SEPA payment information for European Single Euro Payments Area transfers
14 properties 6 required
GetExternalWalletsResponse
array
SpeiAdvancedPaymentInfo
object
Advanced SPEI payment information for Mexican bank transfers with full details
9 properties 6 required
ExternalWalletAsset
object
8 properties
SetCustomerRefIdRequest
object
1 property
UsWirePaymentInfo
object
US Wire payment information for US domestic wire transfers
15 properties 13 required
IbanPaymentInfo
object
IBAN payment information for European bank transfers
11 properties 8 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fireblocks-whitelisted-external-wallets-api-openapi.yml Raw ↑

Other APIs Fireblocks publishes across the network.

Fireblocks Vaults API
Fireblocks Transactions API
Fireblocks Tokenization API
Fireblocks Staking API
Fireblocks NFTs API
Fireblocks Compliance and Policy API
Fireblocks Gas Station API
Fireblocks Webhooks API
fireblocks Approval Requests API
fireblocks Blockchains & Assets API
fireblocks Connected Accounts (Beta) API
fireblocks Contract Interactions API
Where this information came from

This is an independent, third-party profile of fireblocks Whitelisted External Wallets API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.