Complete Summary
Returns complete summary including accepted tokens and their configurations, accepted fiats, user information (fees, settings), and user-specific network rates.
user_info.minimum_payment is the percentage of a payin's crypto_amount that must arrive for it to be marked completed (100 = the full amount, also used when the account has no value set). Rates and limits are numeric strings without trailing zeros ("1", "2.5"). network_rates is keyed by network and only lists networks with an override; its user_pays_* flags are null when the network inherits the account setting. With no overrides, network_rates is an empty array ([]), not an object. Data can be up to 5 minutes old. Rates are explained below. accepted_tokens follows the same rules as Accepted Tokens: This is the platform catalogue of active tokens, one entry per token and network. It is not filtered by your account and does not say whether a token accepts deposits, payouts or both on that network. Availability is checked when you create the operation: a payin needs the token enabled on your account and deposits active on that network (otherwise invalid_parameters on crypto_currency, unsupported_token_or_deposits_disabled or token_network_mismatch); a payout needs withdrawals active on that network (otherwise invalid_parameters, unsupported_token_or_withdrawals_disabled or token_network_mismatch). balance_key is the key of the token in GET /v1/balances and in the balance filter of List Statements.
https://bridge.bifrostcrypto.com/v1/summarystatements:read(a new key with no list is read-only)Headers
| Key | Value | Description |
|---|---|---|
X-Bifrost-Invoke | {{api_key}} | Private API key |
cURL Example
curl -X GET "https://bridge.bifrostcrypto.com/v1/summary" \
-H "X-Bifrost-Invoke: YOUR_API_KEY"Response Example
{
"message": "summary_retrieved_success",
"data": {
"accepted_tokens": [
{
"symbol": "USDT",
"contract_address": "0xdac17f958d2ee523a2206206994597c13d831ec7",
"network": "Ethereum",
"variant": null,
"balance_key": "balance_tether",
"min_receipt": "10",
"max_receipt": "unlimited",
"min_withdrawal": "20",
"max_withdrawal": "50000",
"network_fee": "0.001"
}
],
"accepted_fiats": [
{
"code": "USD",
"name": "US Dollar",
"symbol": "$"
}
],
"user_info": {
"minimum_payment": "10",
"receipt_rate": "2.5",
"payment_rate": "1.5",
"deposit_rate": "2.5",
"withdrawal_rate": "1.5",
"user_pays_payment_network_fee": true,
"user_pays_receipt_network_fee": false,
"user_pays_deposit_network_fee": false,
"user_pays_withdrawal_network_fee": true
},
"network_rates": {
"Ethereum": {
"payment_rate": "1",
"receipt_rate": "2",
"deposit_rate": "2",
"withdrawal_rate": "1",
"user_pays_payment_network_fee": true,
"user_pays_receipt_network_fee": null,
"user_pays_deposit_network_fee": null,
"user_pays_withdrawal_network_fee": null
}
},
"summary_stats": {
"total_tokens": 15,
"total_fiats": 5,
"total_network_overrides": 1,
"generated_at": "2026-01-16 10:00:00"
}
}
}Rates
Percentages charged on each operation. The rate applied to a given payin or payout is returned in its percent_rate field. network_rates overrides these values for the networks it lists.
| Field | Applies to |
|---|---|
payment_rate | Payouts created through the API (POST /v1/payout). |
receipt_rate | Payins created through the API (POST /v1/payin) and deposits to fixed addresses created through the API. |
withdrawal_rate | Withdrawals made in the panel. |
deposit_rate | Deposits received through the panel, including fixed addresses created in the panel. |
user_pays_payment_network_fee · user_pays_receipt_network_fee | true when your account pays the network fee of API payouts / API payins. |
user_pays_withdrawal_network_fee · user_pays_deposit_network_fee | The same for panel withdrawals / panel deposits. |
minimum_payment | Percentage of a payin's crypto_amount that must arrive for it to be marked completed (100 = the full amount). |
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 |
|---|---|---|---|
| 404 | record_not_found | The account setup is incomplete. | Contact support. |
| 500 | internal_error | Unexpected failure. | Nothing was changed. Retry later. |
| 503 | service_unavailable | The token or fiat catalogue could not be loaded. | Nothing was changed. Retry later. |
Other responses
Responses that are not the happy path and still need handling in your integration.
Token or fiat catalogue unavailable
The accepted tokens or fiats could not be loaded. Retry later. A missing account record answers 404 record_not_found (details.resource = user_info); an unexpected failure answers 500 internal_error.
{
"error": {
"code": "service_unavailable",
"message": "Service temporarily unavailable"
}
}