API overview

There are two APIs here and they have nothing in common — different base paths, different auth, different response shapes. Picking the wrong one is the usual first wrong turn.

Marketplace API

Public, no key, read-only.Collections, floors, listings, sales and tokens across every chain.https://exclusivo.one/v1

Store API

API key, scoped, read and write.Your own shop’s products, orders, customers, stock and analytics. Plus webhooks.https://exclusivo.one/api/v1

Side by side

	Marketplace	Store
Base	`/v1`	`/api/v1`
Auth	None	API key
Covers	Everything public	One shop, yours
Methods	`GET`	`GET`, `POST`, `PUT`, `DELETE`
CORS	`*` — call it from a browser	Server-side only
Rate limit	120/min lists, 300/min items, per IP	Per key, per minute
Success	`{ data, pagination?, meta? }`	`{ data, pagination }`
Error	`{ error: { code, message } }`	`{ error: "message" }`
Spec	`/v1/openapi.json`	—

Which one do you want

Floor prices, listings or sales for a collection

Marketplace API. No key needed. → Marketplace API

Syncing products from another system into your shop

Store API, products:write. → Products

Pushing orders into your fulfilment software

Store API with orders:read — or better, a webhook, so you’re not polling.

A public collection tracker with no backend

Marketplace API. It’s CORS-open, so you can call it straight from the browser.

Caching

Marketplace responses are CDN-cached with stale-while-revalidate, so repeated identical requests are cheap and don’t eat your rate limit at the origin. Don’t add cache-busting parameters. The Store API isn’t cached — it returns your live data.

Start here

curl "https://exclusivo.one/v1/collections?chain=solana&limit=5"

# Growth → API in your dashboard, then:
curl https://exclusivo.one/api/v1/products \
  -H "Authorization: Bearer ex_live_your_key_here"

Marketplace API

Store API

​Side by side

​Which one do you want

​Caching

​Start here

Side by side

Which one do you want

Caching

Start here