GET

Get Config

Returns the user's fixed addresses config (limits, enabled status and webhook_url).

Per-type maps are null when the account uses the single global limit. When a per-type map is set it replaces the global limit of that origin, and types missing from the map cannot be created. Returns 403 feature_disabled if the feature is disabled for the user.

GEThttps://bridge.bifrostcrypto.com/v1/fixed-wallets/config

Required scope:wallets:read(a new key with no list is read-only)

Permission of the Guardian Required

"Not every traveler may raise an eternal gate. To hold a portal open and watch its threshold without rest, the vigilant guardian must first grant his blessing: beseech Heimdall, and only then shall your standing stone endure."

Heimdallr Níu-mæðra sonr

ᚱ

"Every eternal pact has its measure: the Allfather decrees how many standing stones a realm may raise, and to which herald the omens shall be sent."

Odin, The Allfather

Headers

Key	Value	Description
`X-Bifrost-Invoke`	`{{api_key}}`	Private API key

cURL Example

bash

curl -X GET "https://bridge.bifrostcrypto.com/v1/fixed-wallets/config" \
  -H "X-Bifrost-Invoke: YOUR_API_KEY"

Response Example

json

{
  "message": "fixed_wallets_config_success",
  "config": {
    "enabled": 1,
    "max_wallets_panel": 5,
    "max_wallets_panel_per_type": null,
    "max_wallets_external_api": 1000,
    "max_wallets_external_api_per_type": {
      "evm": 800,
      "tron": 200
    },
    "webhook_url": "https://your-site.com/webhook-fixed-wallets"
  }
}

Errors

Every error has the shape error.code, error.message and, when useful, error.details. Authentication, scope and rate-limit errors (401, 403, 429) apply to every endpoint and are described under Authentication.

Status	Code	When	What to do
403	`feature_disabled`	Fixed addresses are not enabled for the account.	Contact support.

Other responses

Responses that are not the happy path and still need handling in your integration.

403

Feature disabled

Fixed addresses are not enabled for the account. Ask support to enable them.

json

{
  "error": {
    "code": "feature_disabled",
    "message": "This feature is not enabled for the account"
  }
}