Get Affected Setups Count
Counts how many deployed setups a node- or network-wide fee change would be pushed to, before you make it. A change at those scopes is fanned out to every deployed setup that inherits it (see Fees Overview), so this is the number of setups whose on-chain fees may change.
- With
fee_id(editing an existing row) the count is exact: only setups whose current effective fees take at least one rate from that row are counted. A setup that takes the rate from a more specific row is left out.node_idandnetwork_idare ignored. - Without
fee_id(creating a row) every deployed setup in thenode_id/network_idscope is counted. Both are optional; leaving one out leaves that axis unfiltered, and leaving out both counts every deployed setup.
Only the platform owner node's API key may call this; every other key gets 403.
Required permission: fee:view
Request
GET /v2/admin/fees/affected-setups
Parameters
| Name | Type | In | Description |
|---|---|---|---|
fee_id | string | query | Fee row being edited (24-character hex) |
node_id | string | query | Node scope of the row being created. Used only without fee_id |
network_id | string | query | Network scope of the row being created. Used only without fee_id |
Headers
| Name | Description |
|---|---|
Authorization | Required. Bearer <access_token> |
Example
curl --request GET \
--url '{{baseUrl}}/v2/admin/fees/affected-setups?node_id=6a4bef2b1e781b11c22e9707&network_id=6a4bf0a21e781b11c22e9712' \
--header 'Authorization: Bearer <access_token>'
Response
{
"count": 3
}
Response Fields
| Field | Type | Description |
|---|---|---|
count | integer | Number of distinct deployed setups the change would reach |
Errors
| Status | Code | Description |
|---|---|---|
| 400 | 10016 | fee_id, node_id or network_id is not a 24-character hex ID |
| 403 | 10003 (domain 9) | The key is not the platform owner node's |
| 500 | 10000 | Unexpected server error |
See Errors for the error format and common codes.