A multisig account: threshold, signatories, operations by status
https://api.bittensor.ai/api/v2/multisigs/{account}- Status
- Beta
- Auth
- API key or OAuth access token
- Scope
data:read- Rate limit
plan
What the chain has shown of a multisig account: its threshold and signatories (sorted; from the Multisig calls that acted for it), whether the derivation blake2_256(modlpy/utilisuba ++ signatories ++ threshold) was verified against a Multisig event, the first and last successful call, its operations by status (open, executed, cancelled) and its immediate dispatches (as_multi_threshold_1: no operation, never listed). Accounts as {ss58, hex}. 404 MULTISIG_NOT_KNOWN when no Multisig call has acted for the account: not observed, never 'is not a multisig' (a multisig that has not acted yet is not known). Cached as tip (open operations move with every block). Errors are application/problem+json: INVALID_ADDRESS, MULTISIG_NOT_KNOWN (404), UNKNOWN_PARAMETER, NOT_READY (503), SOURCE_TIMEOUT (503), SOURCE_NOT_READY (503).
Beta: this route may change with one release's notice in the v2 changelog; additive changes need none (x-stability: beta).
Path parameters
- accountpath, required· string
The multisig account: SS58, or 0x + 64 hex. Anything else is a 400
INVALID_ADDRESS.
Query parameters
- includequery· string
Reserved for opt-in sections. This route defines none yet; the parameter is declared so that adding one later is additive for generated clients. Any value is a 400
INVALID_INCLUDE.
Response
data is an object with these fields. Amounts are integer strings in their base unit, and null means unknown, never zero (see Units and formats). meta.at names the block the answer was read at.
The multisig.
- accountobject
The multisig account, as
{ss58, hex}.2 fields in account
- ss58string
The account, SS58 (prefix 42).
- Format: SS58 address
- hexstring
The same 32-byte account id, 0x + 64 lower-case hex (the public key).
- Format: 32-byte hex: 0x and 64 hex digits
- thresholdinteger · unit count
Approvals needed (1 for an account seen only through
as_multi_threshold_1); at least 1.- signatoriesarray of objects · can be null
Every signatory, as
{ss58, hex}, sorted by hex (the runtime's order), each once: the caller plusother_signatoriesof the first call (in chain order) whose derivation a Multisig event verified. At leastthresholdof them. Null when no call's derivation was verified (only threshold-1 dispatches or failed attempts seen).2 fields in signatories (each item)
- ss58string
The account, SS58 (prefix 42).
- Format: SS58 address
- hexstring
The same 32-byte account id, 0x + 64 lower-case hex (the public key).
- Format: 32-byte hex: 0x and 64 hex digits
- derivation_verifiedboolean · can be null
True when blake2_256(
modlpy/utilisuba++ signatories ++ threshold) equals the account a Multisig event named. Null when no Multisig event has been seen yet (only threshold-1 dispatches or failed attempts).- first_seenobject
The first successful Multisig call that acted for it.
2 fields in first_seen
- heightinteger · unit block
The block.
- extrinsic_idstring · unit id
The extrinsic,
{height}-{index}.- Format: block and index, such as 4200000-3
- last_seenobject
The latest successful Multisig call that acted for it.
2 fields in last_seen
- heightinteger · unit block
The block.
- extrinsic_idstring · unit id
The extrinsic,
{height}-{index}.- Format: block and index, such as 4200000-3
- operationsobject
Its operations by status.
3 fields in operations
- openinteger · unit count
Operations still open.
- executedinteger · unit count
Operations executed (the inner call ran, successfully or not).
- cancelledinteger · unit count
Operations cancelled.
- immediateinteger · unit count
Successful
as_multi_threshold_1dispatches: no operation, no deposit, never listed under/operations. The runtime emits MultisigExecuted for them only since about block 6.2M; this counts the calls, all history.
Response headers
10 headers: ETag, Cache-Control, CDN-Cache-Control, X-BTAI-Stale, X-BTAI-Stale-As-Of, RateLimit-Policy, RateLimit, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset
- ETag
Strong validator of this answer. Send it back as
If-None-Match: an unchanged answer is a 304 Not Modified without a body. A settled answer's validator leaves the chain head out, so it stays valid as the head moves.- Cache-Control
One of three classes: settled
public, max-age=3600, stale-while-revalidate=86400(pinned to a block that cannot move), slowpublic, max-age=300, stale-while-revalidate=600(state that moves in minutes or days) or tippublic, max-age=6, stale-while-revalidate=12(follows the chain head); the label routes are cached until the next nightly copy (public, max-age=<seconds>, stale-while-revalidate=60). Neverimmutable.no-storeon an earlier answer served because the data source failed (X-BTAI-Stale).- CDN-Cache-Control
The same class for shared caches (RFC 9213; browsers ignore it): settled 24 h, slow 300 s, tip 6 s, each with
stale-while-revalidateandstale-if-error;no-storewithX-BTAI-Stale.- X-BTAI-Stale
Present only when the data source failed to answer (it timed out or was unavailable) and an earlier answer to the same request is served instead of a 503 (stale if error, RFC 5861). Then
if-error, withX-BTAI-Stale-As-Of,Age(its seconds since then) andWarning: 110 - "Response is Stale", andCache-Control: no-store: the answer is never kept as fresh, and a later request reads again. Prices and quotes are never served this way.- X-BTAI-Stale-As-Of
With
X-BTAI-Stale: when the earlier answer served was produced, an RFC 3339 UTC time (2026-10-21T12:00:00Z).- RateLimit-Policy
The tier's request quota of the current window (IETF draft), e.g.
"tier";q=600.- RateLimit
Requests left in the current window and the seconds until it resets (IETF draft), e.g.
"tier";r=597;t=42.- X-RateLimit-Limit
The tier's request quota of the current window.
- X-RateLimit-Remaining
Requests left in the current window.
- X-RateLimit-Reset
When the current window resets, Unix seconds.
Status codes
200 · 304 · 400 · 401 · 402 · 403 · 404 · 429 · 500 · 502 · 503
304 Not Modified: the If-None-Match validator still matches; no body.
Error codes
The codes this endpoint can return. Each links to what it means and what to do.
- AMBIGUOUS_CREDENTIALS
- BAD_GATEWAY
- BILLING_UNAVAILABLE
- BUDGET_EXCEEDED
- CONCURRENCY_LIMIT
- INSUFFICIENT_PERMISSIONS
- INTERNAL_ERROR
- INVALID_ADDRESS
- INVALID_INCLUDE
- MULTISIG_NOT_KNOWN
- NOT_READY
- PAYMENT_REQUIRED
- PLAN_REQUIRED
- RATE_LIMITED
- SERVICE_UNAVAILABLE
- SOURCE_BUSY
- SOURCE_NOT_READY
- SOURCE_TIMEOUT
- UNAUTHORIZED
- UNKNOWN_PARAMETER
- VALIDATION_ERROR
From the API's published specification, version 1.165.0.