How to Get All ERC-1155 NFTs Owned by a Wallet

Follow this tutorial to learn how to get all ERC-1155 NFTs owned by a wallet.

This tutorial explains the steps in getting a list of Ethereum Mainnet ERC-1155 NFTs owned by any wallet.

Step 1. Use the assets endpoint with the following details:

  • protocol: ethereum

  • network: mainnet

    https://svc.blockdaemon.com/nft/v1/ethereum/mainnet/assets

Step 2. Add the following parameters:

  • wallet address

    • parameter: wallet_address
    • value: e.g. 0x5682035b6b1D04924C7661b09A974fF0695De6bE

  • token type

    • parameter: token_type
    • value: ERC1155

  • wallet filter

    • parameter: show_wallets
    • value: e.g. true
    https://svc.blockdaemon.com/nft/v1/ethereum/mainnet/assets?wallet_address=0x5682035b6b1D04924C7661b09A974fF0695De6bE&token_type=ERC1155&show_wallets=true

📘

Note:

The available token types are ERC20, CRYPTOPUNKS, ERC721, ERC721Enumerable, and ERC1155. However, ERC20 query results are limited to NFT ERCs that use the ERC20 interfaces such as ERC721, ERC721Enumerable, and ERC1155.

Step 3. Execute the query.

For example, in cURL, you should run the following code:

curl -X GET 'https://svc.blockdaemon.com/nft/v1/ethereum/mainnet/assets?wallet_address=0x5682035b6b1D04924C7661b09A974fF0695De6bE&token_type=ERC1155&show_wallets=true' -H 'Authorization: Bearer YOUR_API_KEY'

📘

Note:

To authorize your request, you need to get an API key and use it as a bearer token or a query parameter. Learn more: Authentication Guide

Step 4. Your results will look something like this:

{
    "data": [
        {
            "id": "5e1f4454-34ff-5118-9987-96b481625128",
            "token_id": "9999",
            "image_url": "token/0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D/5e1f4454-34ff-5118-9987-96b481625128.png",
            "name": "#9999",
            "contract_address": "0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D",
            "wallets": [],
            "burned": false
        },
        {...more assets...}
    ],
    "meta": {
        "paging": {
            "next_page_token": "eyJ0b2tlbl9pZCI6OTgyOCwidWlkIjoiNjMzOWIzMWYtNjg1Yi01ZDA1LWIyNmYtNDliNTc2M2E0ZDUzIn0="
        }
    }
}

The response does not contain token types, but you can get them with another endpoint: