Skip to content

Commit 9f8dbe0

Browse files
committed
docs: clarify NFT coverage and limitations in Solana API documentation
1 parent f41d084 commit 9f8dbe0

1 file changed

Lines changed: 16 additions & 0 deletions

File tree

blockapi/v2/api/solana.py

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,22 @@ class SolanaApi(CustomizableBlockchainApi, BalanceMixin):
4141
4242
API docs: https://docs.solana.com/apps/jsonrpc-api
4343
44+
NFT coverage
45+
------------
46+
This API discovers tokens via ``getTokenAccountsByOwner`` (SPL and
47+
Token-2022 programs). NFTs that use these programs (e.g. Metaplex
48+
legacy, pNFT, Token-2022 NFTs) **are** returned when
49+
``include_nfts=True``.
50+
51+
However, **Metaplex Core assets (MplCoreAsset)** are NOT SPL tokens —
52+
they have no mint or token account. They won't appear in
53+
``getTokenAccountsByOwner`` results, so this API cannot see them.
54+
They *are* reachable via the DAS RPC method ``getAssetsByOwner``,
55+
but this API does not use that method (it uses ``getAssetBatch``
56+
only to enrich metadata for tokens already found on-chain).
57+
To get full NFT coverage, use a dedicated NFT provider such as
58+
``MagicEdenSolanaApi`` alongside this API.
59+
4460
Caching architecture
4561
--------------------
4662
``_das_cache`` and ``_ban_list`` are **class-level** attributes shared

0 commit comments

Comments
 (0)