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

starknet_specVersion - STRK

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

This method returns the version of the Starknet JSON-RPC specification that the node implements. It is used to confirm compatibility before issuing version-sensitive calls.

Parameters

This method does not require any parameters. Send the request with an empty params array.

Request

curl --location --request POST 'https://shared.eu-central-1.getblock.io/<ACCESS-TOKEN>/' \
--header 'Content-Type: application/json' \
--data-raw '{
    "jsonrpc": "2.0",
    "method": "starknet_specVersion",
    "params": [],
    "id": "getblock.io"
}'
example.js
const axios = require('axios');

const response = await axios.post('https://shared.eu-central-1.getblock.io/<ACCESS-TOKEN>/', {
    jsonrpc: '2.0',
    method: 'starknet_specVersion',
    params: [],
    id: 'getblock.io'
}, {
    headers: { 'Content-Type': 'application/json' }
});

console.log(response.data.result);
example.py
import requests

response = requests.post(
    'https://shared.eu-central-1.getblock.io/<ACCESS-TOKEN>/',
    headers={'Content-Type': 'application/json'},
    json={
        'jsonrpc': '2.0',
        'method': 'starknet_specVersion',
        'params': [],
        'id': 'getblock.io'
    }
)

print(response.json())

Response

{
    "jsonrpc": "2.0",
    "id": "getblock.io",
    "result": "0.8.1"
}

Response Parameters

Parameter
Type
Description

jsonrpc

string

JSON-RPC protocol version ("2.0")

id

string

Request identifier matching the request

result

string

Semantic version of the supported JSON-RPC spec

Use Cases

  • Compatibility Checks: Confirm the node's spec version before calling newer methods

  • Client Negotiation: Select request shapes that match the served spec

  • Diagnostics: Report the spec version when filing an issue

  • Monitoring: Track spec upgrades across an endpoint fleet

Error Handling

Error
Message
Description

63 / UNEXPECTED_ERROR

Unexpected error

The node failed to return its spec version

403 / RBAC: access denied

Access denied

The GetBlock access token is missing or incorrect

Last updated

Was this helpful?