> ## Documentation Index > Fetch the complete documentation index at: https://coinstats.app/api-docs/llms.txt > Use this file to discover all available pages before exploring further. # Get NFT Collection Owners > Get the holders of an NFT collection, largest first. > [!NOTE] > > **20** credits per request *** > **You will get** > > * Holder addresses with token counts > * Total holder count > **Required** > > * collectionAddress: Path parameter. NFT collection contract address. > **Optional** > > * blockchain: Chain the collection lives on. Defaults to ethereum. > * page & limit: Control pagination; limit is capped at 100. ## OpenAPI ````yaml /api-docs/api-reference/openapi.json get /v1/nft/collection/{collectionAddress}/owners openapi: 3.0.0 info: title: CoinStats Public API description: >- CoinStats Public API — programmatic access to market data, news, NFTs, wallets, exchange connections, and user portfolios. Authenticate every request with the `X-API-KEY` header (or an OAuth Bearer token in the `Authorization` header). Generate keys at https://openapi.coinstats.app. version: '1.0' contact: {} servers: - url: https://api.coinstats.app security: [] tags: - name: CoinStats description: '' - name: Market Data description: >- The Market Data section of the API provides endpoints to access a wide range of market-related information, including cryptocurrency coins, ticker data, and fiat currency rates. This category offers comprehensive data to help users monitor and analyze the cryptocurrency market, track prices, and gain insights into market trends - name: RWA description: >- Tokenized real-world assets: overview, stocks, commodities, ETFs, tokens, trading markets, and aggregate or per-asset history. - name: News description: >- The News section of the API allows you to access news articles and updates related to cryptocurrencies and the blockchain industry. It provides valuable information from various sources to keep you informed about the latest developments - name: NFTs description: >- The NFT section of the API provides endpoints to interact with Non-Fungible Tokens (NFTs), which are unique digital assets stored on a blockchain. These endpoints allow you to retrieve information about NFTs, including collections, assets, trending NFTs, and specific assets associated with wallet addresses. - name: Wallet NFTs description: >- NFTs held by a wallet: tokens, collections, value, activity and token gating - name: Wallet Data description: >- The Wallet section of the API provides a comprehensive set of endpoints to manage and interact with wallets. It enables users to retrieve wallet balances, monitor syncing status, fetch transaction data, and synchronize wallet information with the blockchain. By integrating these endpoints into your application, you can offer robust wallet functionality to your users. - name: Exchange Connection description: >- The Exchange Connection section of the API provides a comprehensive set of endpoints to manage and interact with exchanges. It enables users to retrieve exchange balances, monitor syncing status, fetch transaction data. By integrating these endpoints into your application, you can offer robust exchange portfolio tracking functionality to your users. - name: User Portfolio description: >- The Portfolio section of the API provides a comprehensive set of endpoints to manage and interact with Share Portfolios. It enables users to retrieve current Portfolio Coins and Transactions. - name: Usage description: The Usage section provides account-level API usage data. - name: Status description: The Status section provides API availability checks. - name: Prediction · Markets description: >- Polymarket, Kalshi and Polymarket US markets: list/trend/detail, live prices and order book, OHLC candles, and price history. `view` picks the venues a list shows (`intl` default, `us`, `all`). Prices are probabilities in 0..1, money is USD, dates are ISO 8601. - name: Prediction · Events description: >- Polymarket, Kalshi and Polymarket US events — groups of related markets (e.g. one market per candidate). List, trend, and fetch an event with its child markets. - name: Prediction · Traders description: >- Trader leaderboard plus deep per-trader analytics: profile, open positions, trade history, daily PnL, category stats, aggregate trade stats, and composite score. - name: Prediction · Analytics description: >- Platform-wide analytics: overview stats, smart-money and whale traders, trending-by-smart-money markets, and composite market signals. - name: Prediction · Search description: Full-text search across prediction-market events, markets, and traders. paths: /v1/nft/collection/{collectionAddress}/owners: get: tags: - NFTs summary: Get the holders of an NFT collection, largest first. operationId: get-nft-collection-owners parameters: - name: collectionAddress required: true in: path description: The address of the NFT collection schema: type: string example: '0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d' - name: page required: false in: query description: Page number to retrieve (1-based indexing) schema: type: number example: 1 - name: limit required: false in: query description: Number of NFT items to return per page schema: type: number example: 20 - name: blockchain required: false in: query description: >- The blockchain network identifier from [/wallet/blockchains](/openapi/get-blockchains) call response (its `chain` field). NFT data is available on: ethereum, polygon-pos, base, arbitrum-one, optimistic-ethereum, zksync, blast, linea, scroll, zora, abstract, apechain, avalanche, binance_smart, unichain, soneium, berachain, world-chain, celo, xdai, monad. Defaults to ethereum. schema: default: ethereum example: ethereum type: string enum: - ethereum - polygon-pos - base - arbitrum-one - optimistic-ethereum - zksync - blast - linea - scroll - zora - abstract - apechain - avalanche - binance_smart - unichain - soneium - berachain - world-chain - celo - xdai - monad responses: '200': description: '' content: application/json: schema: $ref: '#/components/schemas/NftCollectionOwnersPageDto' '400': description: Bad Request content: application/json: example: statusCode: 400 message: Bad Request requestId: 11111111-2222-3333-4444-555555555555 path: '401': description: Unauthorized content: application/json: example: statusCode: 401 message: Unauthorized requestId: 11111111-2222-3333-4444-555555555555 path: '403': description: Forbidden content: application/json: example: statusCode: 403 message: Forbidden requestId: 11111111-2222-3333-4444-555555555555 path: '404': description: Not Found content: application/json: example: statusCode: 404 message: Not Found requestId: 11111111-2222-3333-4444-555555555555 path: '409': description: Conflict (for some endpoints) content: application/json: example: statusCode: 409 message: Transactions not synced requestId: 11111111-2222-3333-4444-555555555555 path: '429': description: Too Many Requests content: application/json: example: statusCode: 429 message: Rate limit exceeded requestId: 11111111-2222-3333-4444-555555555555 path: '503': description: Service Unavailable content: application/json: example: statusCode: 503 message: Service Unavailable. Please Contact Support security: - X-API-KEY: [] x-codeSamples: - lang: curl label: cURL source: |- curl --request GET \ --url 'https://api.coinstats.app/v1/nft/collection/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d/owners' \ --header 'X-API-KEY: ' - lang: python label: Python source: >- import requests url = "https://api.coinstats.app/v1/nft/collection/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d/owners" headers = {"X-API-KEY": ""} response = requests.request("GET", url, headers=headers) print(response.json()) - lang: javascript label: JavaScript source: >- const options = {method: 'GET', headers: {'X-API-KEY': ''}}; fetch('https://api.coinstats.app/v1/nft/collection/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d/owners', options) .then((response) => response.json()) .then((response) => console.log(response)) .catch((err) => console.error(err)); - lang: php label: PHP source: |- "https://api.coinstats.app/v1/nft/collection/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d/owners", CURLOPT_RETURNTRANSFER => true, CURLOPT_CUSTOMREQUEST => "GET", CURLOPT_HTTPHEADER => [ "X-API-KEY: " ], ]); $response = curl_exec($curl); $err = curl_error($curl); curl_close($curl); if ($err) { echo "cURL Error #:" . $err; } else { echo $response; } - lang: go label: Go source: "package main\n\nimport (\n\t\"fmt\"\n\t\"io\"\n\t\"net/http\"\n)\n\nfunc main() {\n\n\turl := \"https://api.coinstats.app/v1/nft/collection/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d/owners\"\n\n\treq, _ := http.NewRequest(\"GET\", url, nil)\n\n\treq.Header.Add(\"X-API-KEY\", \"\")\n\n\tres, _ := http.DefaultClient.Do(req)\n\n\tdefer res.Body.Close()\n\tbody, _ := io.ReadAll(res.Body)\n\n\tfmt.Println(string(body))\n}" - lang: java label: Java source: >- HttpResponse response = Unirest.get("https://api.coinstats.app/v1/nft/collection/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d/owners") .header("X-API-KEY", "") .asString(); components: schemas: NftCollectionOwnersPageDto: type: object properties: data: type: array items: $ref: '#/components/schemas/NftCollectionOwnerDto' meta: $ref: '#/components/schemas/PageMetaDto' ownersCount: type: number description: Total holders, when the collection has 50,000 or fewer example: 5616 nullable: true truncated: type: boolean description: >- The collection has more than 50,000 holders; only the first 50,000 were ranked example: false required: - data - meta - ownersCount - truncated NftCollectionOwnerDto: type: object properties: address: type: string example: '0x46efbaedc92067e6d60e84ed6395099723252496' tokenCount: type: number description: Tokens held in the collection example: 3 required: - address - tokenCount PageMetaDto: type: object properties: page: type: number description: Current page number (1-based) example: 2 minimum: 1 limit: type: number description: Number of items per page example: 20 minimum: 1 maximum: 1000 itemCount: type: number description: Total number of items across all pages example: 150 minimum: 0 pageCount: type: number description: Total number of pages available example: 8 minimum: 0 hasPreviousPage: type: boolean description: Whether there is a previous page available example: true hasNextPage: type: boolean description: Whether there is a next page available example: true required: - page - limit - itemCount - pageCount - hasPreviousPage - hasNextPage securitySchemes: X-API-KEY: type: apiKey in: header name: X-API-KEY description: >- API key required to access the endpoints. Generate one from your dashboard at https://openapi.coinstats.app and pass it in the `X-API-KEY` request header. Never expose your key in client-side code. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.