Fetch Multi-Wallet NFT Balances API avatar

Fetch Multi-Wallet NFT Balances API

Pricing

Pay per usage

Go to Apify Store
Fetch Multi-Wallet NFT Balances API

Fetch Multi-Wallet NFT Balances API

Solana API endpoint for fetching multi-wallet NFT balances with collection metadata, floor prices, and aggregated portfolio values across multiple wallets. Docs: https://docs.vybenetwork.com/reference/post_wallet_nfts_many_v4

Pricing

Pay per usage

Rating

0.0

(0)

Developer

Vybe Network

Vybe Network

Maintained by Community

Actor stats

1

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Fetch Multi-Wallet NFT Balances

Solana API Summary

Fetch Multi-Wallet NFT Balances

Solana API Description

Solana API endpoint for fetching multi-wallet NFT balances with collection metadata, floor prices, and aggregated portfolio values across multiple wallets.

This Solana API actor is designed for search visibility and developer onboarding, with practical endpoint context, strong keyword coverage, and direct doc links for implementation.

Explore docs here: Fetch Multi-Wallet NFT Balances Docs and Solana API Docs.

Solana API Usage

Use this endpoint for Solana analytics, token and market intelligence, wallet behavior analysis, and trading automation. The actor follows the official Vybe OpenAPI contract for consistent and accurate integrations.

Request Body Fields

  • includeNoPriceBalance (boolean, optional) - Whether or not we should include NFTs we do not track prices for.
  • limit (integer, optional) - The limit of entries to return (per wallet). If not passed, first 1000 entries are returned (the maximum).
  • ownerAddresses (array, required) - Wallets to include in the returned results (max 10).
  • ownerAddresses[] (string, nested) - Typed Solana public key identifier used across request parameters and response fields.
  • page (integer, optional) - The requested page.
  • sortByAsc (string, optional) - Sort ascending based on amount or value of positions. Only one of sort_by_asc or sort_by_desc can be used
  • sortByDesc (string, optional) - Sort descending based on amount or value of positions. Only one of sort_by_asc or sort_by_desc can be used

Responses

  • 200: Successful response
  • 400: Invalid request
  • 500: Internal server error

Resources