get https://api.fireblocks.io/v1/network_connections//is_third_party_routing/
The Fireblocks Network allows for flexibility around incoming deposits. A receiver can receive network deposits to locations other than Fireblocks. This endpoint validates whether future transactions are routed to the displayed recipient or to a 3rd party.
A receiver can receive network deposits to locations other than Fireblocks. This endpoint validates whether future transactions are routed to the displayed recipient or to a 3rd party.
Note: This API call is subject to Flexible Routing Schemes.
Your routing policy defines how your transactions are routed.
You can choose 1 of the 3 different schemes mentioned below for each asset type:
NONE
; Defines the profile routing to no destination for that asset type. Incoming transactions to asset types routed toNone
will fail.CUSTOM
; Route to an account that you choose. If you remove the account, incoming transactions will fail until you choose another one.DEFAULT
; Use the routing specified by the network profile the connection is connected to. This scheme is also referred to as "Profile Routing"
Default Workspace Presets:
- Network Profile Crypto →
CUSTOM
- Note: By default,
CUSTOM
routing scheme uses (dstId
=0
,dstType
=VAULT
).
- Note: By default,
- Network Profile FIAT →
NONE
- Network Connection Crypto →
DEFAULT
- Network Connection FIAT →
DEFAULT