Skip to main content
POST
/
#particle_crosschain_getNFTs
crosschainGetNFTs
curl --request POST \
  --url 'https://rpc.particle.network/evm-chain/#particle_crosschain_getNFTs' \
  --header 'Authorization: Basic <encoded-value>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "particle_crosschain_getNFTs",
  "chainId": 1,
  "params": [
    "<unknown>"
  ]
}
'
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "nfts": [
      {
        "address": "<string>",
        "isSemiFungible": true,
        "tokenId": "<string>",
        "tokenBalance": "<string>",
        "tokenURI": "<string>",
        "name": "<string>",
        "symbol": "<string>",
        "image": "<string>",
        "data": {}
      }
    ]
  }
}

​
Understanding crosschain_getNFTs

  • crosschain_getNFTs is an alternative to getNFTs in which NFTs (ERC-721 tokens) can be retrieved for a given address across multiple different EVM chains in the same query. It takes:
    • Addresses - an array of strings (either one or more account addresses.)
    • Chain IDs - an array of integers.
    • Contracts - (optional) an array of strings. It filters based upon specific collection contracts.

​
Query example

JavaScript
const axios = require('axios');

(async () => {
    const response = await axios.post('https://rpc.particle.network/evm-chain', {
        chainId: 1,
        jsonrpc: '2.0',
        id: 1,
        method: 'particle_crosschain_getNFTs',
        params: [
                ['0x6a2C3C4C7169d69A67ae2251c7D765Ac79A4967e', '0xf584F8728B874a6a5c7A8d4d387C9aae9172D621'],
                [1, 4, 137, 80001]
            ],
    }, {
        auth: {
            username: 'Your Project Id',
            password: 'Your Project Server Key',
        }
    });

    console.log(response.data);
})();

Authorizations

​
Authorization
string
header
required

Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.

Body

application/json
​
jsonrpc
string
default:2
required

Version of the JSON-RPC protocol, should be 2.0.

Example:

"2.0"

​
id
integer
default:1
required

The request identifier.

Example:

1

​
method
enum<string>
required

API method being called.

Available options:
particle_crosschain_getNFTs
​
chainId
integer
required

The chain ID.

Example:

1

​
params
any[]
required

Parameters for the API method call.

Response

200 - application/json

Success

​
jsonrpc
string

Version of the JSON-RPC protocol, should be 2.0.

Example:

"2.0"

​
id
integer

The request identifier.

Example:

1

​
result
object