Skip to main content
PATCH
Update chain IDs within subscription

Authorizations

Authorization
string
header
required

To test endpoints here, paste your API key from the dashboard into the username field and leave the password empty.

Path Parameters

subscription_id
string
required

ID of the subscription

Example:

"77e77447-1586-40e8-a75b-467ef939a0b1"

Body

application/json
chain_ids
string[]

The list of new chain IDs to replace the current associated chain IDs in the subscription. Only chains reporting both supports_transactions and supports_positions in the flags of GET /v1/chains/ are accepted here. Naming a chain that fails that gate returns 400 rather than an empty result, with detail reading chain <id> does not support transactions. That detail names the endpoint's capability rather than the flag that failed, so bob is refused with chain bob does not support transactions even though it reports supports_transactions — what it lacks is supports_positions. Leave the list empty to cover every chain that passes the gate; chains that fail it are left out silently, with no error and no meta signal.

A chain ID.

Response

Successfully updated chain IDs