Community-driven NFT marketplace on Ethereum and Arbitrum with an open SDK (`@looksrare/sdk-v2`) for creating, signing, and fulfilling LooksRare V2 orders, plus a public REST API for collections, listings, offers, and events.
- 01EVM NFT marketplace integrations
- 02creating/fulfilling LooksRare V2 orders
- 03collection + token metadata reads
- 04rewards / staking surfaces
- 05Arbitrum NFT support
- pnpm add @looksrare/sdk-v2 ethers
| Variable | Scope | Description |
|---|---|---|
| LOOKSRARE_API_KEY | Server | LooksRare API key (request via the developer form). Required for elevated rate limits and POST endpoints. Server-only. |
| NEXT_PUBLIC_LOOKSRARE_CHAIN_ID | Client | Chain ID — 1 (Ethereum mainnet) or 42161 (Arbitrum One). |
Use `@looksrare/sdk-v2` for orders: `const lr = new LooksRare(chainId, provider, signer)`, then `lr.createMakerAsk({ collection, tokenId, price, ... })` returns an `{ maker, isCollectionApproved, isTransferManagerApproved }` tuple. Sign with `lr.signMakerOrder(maker)` and submit to the public API: `POST https://api.looksrare.org/api/v2/orders` with header `X-Looks-Api-Key: LOOKSRARE_API_KEY`. To fulfill, fetch with `GET /api/v2/orders?status=VALID&collection=…` and call `lr.executeOrder(order, signature, recipient)`. Reads (collections, tokens, events) live under `/api/v2/collections/{address}` and `/api/v2/tokens`.
- ⚑LooksRare V2 is a separate contract suite from V1 — V1 orders are no longer createable; ensure you use `sdk-v2` (not the deprecated `@looksrare/sdk`) or signature validation will fail.
- ⚑Royalty enforcement: LooksRare honors EIP-2981 + the LooksRare Royalty Fee Registry; collections without registry entries default to 0% royalty even if the contract returns a `royaltyInfo`.
- ⚑Marketplace protocol fee is currently 0.5% (subject to change via governance) — always read the live fee from the contract or `/api/v2/strategies` rather than hardcoding.
- ⚑Chain coverage is Ethereum + Arbitrum only as of 2026; Polygon and other chains are not supported.
- ⚑API key is required for most write endpoints and for >2 req/s read traffic; unkeyed requests are throttled aggressively.
- ⚑TransferManager must be approved per collection before listing — `sdk-v2` exposes `approveErc721` / `approveErc1155` helpers; skipping approval results in an on-chain revert at execute time.