> ## Documentation Index
> Fetch the complete documentation index at: https://docs.uniblock.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# NFT Marketplaces and Discovery

> Build NFT marketplace, discovery, and collection experiences with Uniblock NFT APIs and webhook support.

Uniblock can cover most of the read-heavy data layer for NFT products: collection metadata, item metadata, wallet holdings, floor prices, sales, listings, and ownership. That makes it a practical fit for marketplace frontends, collector dashboards, and collection discovery tools.

## Best-fit workflows

* Collection landing pages
* NFT detail pages
* Wallet ownership and portfolio views
* Sales and floor-price monitors
* Real-time event streams for transfers and contract events

***

## Recommended APIs

* `GET /nft/collection-metadata`
* `GET /nft/nft-in-collection`
* `GET /nft/metadata`
* `GET /nft/floor-price`
* `GET /nft/sales`
* `GET /nft/owners/nft`
* `GET /nft/owners/contract`
* `GET /nft/transfers`
* `GET /nft/transfers/nft`

Start from the [NFT API overview](/reference/unified-api/api-overview-nft) for endpoint coverage.

***

## Suggested implementation flow

### 1. Build the collection page

At minimum, load:

* collection metadata
* a paginated list of NFTs in the collection
* floor price
* recent sales

That gives you the baseline marketplace browsing experience.

### 2. Build the asset page

For each NFT detail page, combine:

* `GET /nft/metadata`
* `GET /nft/transfers/nft`
* `GET /nft/owners/nft`

This gives you provenance, owner state, and transfer history.

### 3. Build the owner experience

For user profiles and portfolio views, combine:

* `GET /nft/balance`
* `GET /nft/owned-collections`
* token endpoints if the same app also shows fungible positions

### 4. Add event-driven updates

Use contract-event webhooks or NFT-focused templates from the webhook flow to:

* refresh collection activity feeds
* notify on transfers
* track popular contracts and major sales activity

***

## Where Direct API fits

NFT products often need marketplace-specific or provider-specific capabilities. When the unified schema is not enough, use [Direct API](/reference/direct/direct-providers/overview) for deeper marketplace or provider integrations while keeping Unified API as the default read layer.

***

## Common pitfalls

<Warning>
  NFT metadata can change over time. Refresh metadata and floor-price data on
  separate schedules instead of treating them as equally fresh.
</Warning>

<Warning>
  Ownership for ERC-1155 assets can involve multiple holders. Do not model all
  NFT ownership as single-owner ERC-721 behavior.
</Warning>

***

## Related docs

* [NFT API overview](/reference/unified-api/api-overview-nft)
* [Webhook quickstart](/reference/webhook/webhook-quickstart)
* [Contract event webhook type](/reference/webhook/webhook-types/event-trigger-contract-event)
* [Address activity webhook type](/reference/webhook/webhook-types/event-trigger-address-activity)