Skip to main content
GET
/
connected_accounts
/
{accountId}
/
allowlist
/
{allowlistId}
TypeScript
const response: Promise<FireblocksResponse<AllowlistEntry>> = fireblocks.connectedAccountsBeta.getConnectedAccountAllowlistEntry(connectedAccountsBetaApiGetConnectedAccountAllowlistEntryRequest);
{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "address": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb",
  "assets": [
    "BTC",
    "ETH"
  ],
  "networks": [
    "ETHEREUM",
    "POLYGON"
  ],
  "status": "ACTIVE",
  "addedAt": "2024-01-15T10:30:00Z",
  "label": "Coinbase Hot Wallet",
  "addressIdentifier": null,
  "providerReferenceId": "CB-SAMPLE-001",
  "providerMetadata": {
    "coinbase_exchange_id": "1234567890"
  }
}

Path Parameters

​
accountId
string
required

The connected account identifier

​
allowlistId
string
required

The Fireblocks allowlist entry identifier

Response

Allowlist entry response

​
id
string<uuid>
required

Unique identifier for the allowlist entry

Example:

"550e8400-e29b-41d4-a716-446655440000"

​
address
string
required

The blockchain address

Example:

"0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb"

​
assets
string[]
required

Assets approved for this address.

Each value is either a Fireblocks asset ID (when the provider's asset maps to a Fireblocks-supported asset) or the raw provider asset symbol (when no mapping exists). Treat values as opaque strings.

Possible combinations:

  • One or more specific asset values (e.g., ["BTC", "ETH"])

See List assets for the canonical list of Fireblocks asset IDs.

Example:
["BTC", "ETH"]
​
networks
string[]
required

Networks approved for this address.

Each value is either a Fireblocks network ID (when the provider's network maps to a Fireblocks-supported blockchain) or the raw provider blockchain identifier (when no mapping exists). Treat values as opaque strings.

Possible combinations:

  • One or more specific network values (e.g., ["ETHEREUM", "POLYGON"])

See List blockchains for the canonical list of Fireblocks blockchain identifiers.

Example:
["ETHEREUM", "POLYGON"]
​
status
enum<string>
required

Current status of the allowlist entry.

  • ACTIVE — Entry is approved and usable.
  • PENDING_PROVIDER_COOLDOWN — Entry was recently added or modified and is in the provider-enforced cooldown window before becoming active.
  • PENDING_PROVIDER_REVIEW — Entry is awaiting provider-side review.
  • PENDING_APPROVAL — Entry is awaiting customer/admin approval on the Fireblocks side.
  • REJECTED — Entry was rejected at submission time and will not become active.
  • REMOVED — Entry was deactivated after previously being active. May still appear in results for audit purposes.
Available options:
ACTIVE,
PENDING_PROVIDER_COOLDOWN,
PENDING_PROVIDER_REVIEW,
PENDING_APPROVAL,
REJECTED,
REMOVED
Example:

"ACTIVE"

​
addedAt
string<date-time>
required

ISO 8601 timestamp when entry was added

Example:

"2024-01-15T10:30:00Z"

​
label
string | null

Human-readable label for the address

Example:

"Coinbase Hot Wallet"

​
addressIdentifier
string | null

Additional identifier (e.g., memo, destination tag)

Example:

null

​
providerReferenceId
string | null

Provider's internal reference ID

Example:

"CB-SAMPLE-001"

​
providerMetadata
object

Provider-specific pass-through data for this address. Treat as an opaque blob: the shape, set of keys, and value types vary by provider, by entry, and over time. Keys may be added, renamed, or removed without notice as providers evolve their integrations or as new providers are added. The example below illustrates one possible shape and is not a contract — do not program against specific keys.

Example:
{ "coinbase_exchange_id": "1234567890" }