Dokumentation / API-Referenz / Gamma
Get Gamma Deposits
Referenz
Zuletzt geprüft am 2026-11-10
Current deposits ordered by largest balance.
Try it
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
netuid | query | string | Filter by one or more subnet IDs. | |
hotkey | query | string | Filter by hotkey (SS58 or 0x-hex). | |
coldkey | query | string | Filter by coldkey (SS58 or 0x-hex). | |
spender | query | string | Filter by deposit spender (SS58 or 0x-hex). | |
page | query | integer (int32) | Page number, starting at 1. Default: 1. Bounded window: (page − 1) × limit must be below 1,000,000. | |
limit | query | integer (int32) | Results per page. Default: 50; maximum: 200. |
Responses
200 — Open Gamma deposits with spendable amount at the newest finalized block reached by the Gamma indexer
| Field | Type | Required | Description |
|---|---|---|---|
data | array | Yes | |
data[].balance | string | Yes | Current Gamma balance, as a decimal string. |
data[].block_number | integer (int32) | Yes | Block at which this deposit last changed. |
data[].bucket_available | string | Yes | Gamma units available in the refill bucket before time-based refill. |
data[].bucket_block | string | Yes | Block at which the refill bucket was last updated. |
data[].change | array | Yes | Event kinds that changed this deposit in its latest changed block. |
data[].change[] | string | Yes | Event or silent cause recorded in a deposit's change array. One of mint, move, spend, set_spender, set_cap, close, coldkey_swap, written_off. |
data[].coldkey | string | Yes | Coldkey that owns this deposit. |
data[].daily_spend_cap | string, nullable | Yes | Daily Gamma spend cap, or null when there is no cap. |
data[].deposit_exists | boolean | Yes | Whether a deposit exists. Always true on this current-state route. |
data[].hotkey | string | Yes | Hotkey that owns this deposit. |
data[].netuid | integer (int32) | Yes | Subnet ID. |
data[].spendable_block | integer (int32) | Yes | Finalized block used to calculate spendable_now. |
data[].spendable_now | string | Yes | Gamma that can be spent at spendable_block, as a decimal string. |
data[].spender | string | Yes | Account allowed to spend this deposit. |
data[].timestamp | string | Yes | Timestamp of the block at which this deposit last changed. |
pagination | object | Yes | Pagination metadata appended to collection responses. next_page / prev_page are explicitly required+nullable in the OpenAPI spec: per docs/api_standards.md we emit null rather than omitting the field, so the SDK should model them as Option/nullable types that are always present in the response. total_items is the exact number of matching rows on every route (issue #992). It used to stop at 1,000,000, which reported a million transfers when finney holds 7,513,252 and a million events when the real figure is 981,179,110; the cap was removed on 29 Sep 2026 and nothing may reintroduce one — crate::pagination::exact_count_sql is the only count form, and no_capped_count_reaches_the_api_surface in data-debug-scripts fails the build if a capped one comes back. total_pages is still bounded, to crate::pagination::max_reachable_page(per_page), because the page parameter is capped to a 1,000,000-row window: deep OFFSET paging reads every skipped row (24.7M rows / 36.6 GiB / 42 s measured on one endpoint, issue #413). So total_pages is exactly the last page this API will serve and next_page / prev_page stay coherent at the window edge, while total_items tells the caller how many rows there really are. History beyond the window is reached with each endpoint's range filters, not a larger page. |
pagination.current_page | integer (int32) | Yes | 1-indexed page that produced the rows in data. |
pagination.next_page | integer (int32), nullable | Yes | Next page number, or null if this is the last page. |
pagination.per_page | integer (int32) | Yes | Number of items requested per page. |
pagination.prev_page | integer (int32), nullable | Yes | Previous page number, or null if this is the first page. |
pagination.total_items | integer (int64) | Yes | Number of items matching the query across all pages. This is the exact count — every matching row, however many there are. It is not bounded by total_pages, so a listing can legitimately report far more items than total_pages × per_page. |
pagination.total_pages | integer (int32) | Yes | Number of pages at the current per_page that this API will serve: ceil(total_items / per_page), capped at ceil(1000000 / per_page) because the page parameter only reaches into the first 1,000,000 rows. When the cap bites, total_items is still the true total and this is the last page a request can ask for; reach deeper history with the endpoint's range filters instead of a larger page. |
400 — Invalid query parameter
| Field | Type | Required | Description |
|---|---|---|---|
message | string | Yes | Plain-english message describing the failure from the caller's perspective. |
status_code | integer (int32) | Yes | HTTP status code (mirrored in the response status line for convenience). |
500 — Internal server error
| Field | Type | Required | Description |
|---|---|---|---|
message | string | Yes | Plain-english message describing the failure from the caller's perspective. |
status_code | integer (int32) | Yes | HTTP status code (mirrored in the response status line for convenience). |
503 — Current deposit state is newer than the block used to calculate spendability
| Field | Type | Required | Description |
|---|---|---|---|
message | string | Yes | Plain-english message describing the failure from the caller's perspective. |
status_code | integer (int32) | Yes | HTTP status code (mirrored in the response status line for convenience). |
Every request needs an Authorization header holding your API key — see Getting started with the Taostats API.