For the complete documentation index, see llms.txt. This page is also available as Markdown.

chain_unsubscribeAllHeads - Bittensor

Example code for the chain_unsubscribeAllHeads JSON-RPC method. Complete guide on how to use chain_unsubscribeAllHeads JSON-RPC in GetBlock Web3 documentation.

Cancels an active heads subscription created by chain_subscribeNewHeads or chain_subscribeFinalizedHeads. The subscription ID must match.

Substrate native JSON-RPC method. Call against a GetBlock endpoint configured for the Substrate interface. For typed SDK access, use Polkadot.js (TypeScript) or substrateinterface (Python).

Parameters

Parameter
Type
Required
Description

subscriptionId

string

Yes

Subscription ID to cancel

Request Example

curl --location --request POST 'https://go.getblock.io/<ACCESS-TOKEN>/' \
--header 'Content-Type: application/json' \
--data-raw '{
    "jsonrpc": "2.0",
    "method": "chain_unsubscribeAllHeads",
    "params": [
        "9DZyB1n6BvF5dQ8wQRhgrxqCw"
    ],
    "id": "getblock.io"
}'
import axios from 'axios';

const data = JSON.stringify({
    "jsonrpc": "2.0",
    "method": "chain_unsubscribeAllHeads",
    "params": [
        "9DZyB1n6BvF5dQ8wQRhgrxqCw"
    ],
    "id": "getblock.io"
});

const config = {
    method: 'post',
    url: 'https://go.getblock.io/<ACCESS-TOKEN>/',
    headers: {
        'Content-Type': 'application/json'
    },
    data: data
};

axios(config)
    .then(response => console.log(JSON.stringify(response.data, null, 2)))
    .catch(error => console.log(error));

Response Example

Response Parameters

Field
Type
Description

result

boolean

true if the subscription was cancelled

Use Cases

  • Resource cleanup when a live feed is no longer needed

  • Connection lifecycle management

Error Handling

Status Code
Error Message
Cause

403

Forbidden

Missing or invalid <ACCESS-TOKEN>

-32602

Invalid params

Request parameters are missing or malformed

-32601

Method not found

Method does not exist on this interface — check whether you're calling a Substrate method on an EVM endpoint or vice versa

-32603

Internal error

Server-side error while processing the request

429

Too Many Requests

Rate limit exceeded for your plan

SDK Integration

Last updated

Was this helpful?