401 or 403 from api.opensea.io
Check Is the key in the X-API-KEY header, and has an instant free-tier key passed its seven days?
Fix Create a full key under Settings > Developer and send it in the header.
Read collections, floors and sales from networks that block OpenSea — one stable exit per researcher and key, within OpenSea's rules.
OpenSea is blocked on several networks. In mainland China, GreatFire's last test of opensea.io (June 2026) was blocked, its API host sits under the same blocked domain, and magiceden.io was blocked in August 2026. From Russia, OONI's measurements between 18 September and 18 October 2026 found opensea.io blocked, nearly all of them confirmed by a block page. Researchers on those networks need an exit abroad to read the marketplace at all.
OpenSea's API works with your own key. Requests carry the key in an X-API-KEY header; instant free-tier keys expire after seven days, full keys come from Settings > Developer — up to three per account — and your limits arrive in the response headers. Collection stats such as floor price, owners, sales and volume come from /api/v2/collections/{slug}/stats.
OpenSea's rules shape the setup. Its terms, updated on 7 October 2026, prohibit using multiple IP addresses or obscuring traffic sources against its access controls, rate limits or traffic filters; its API terms prohibit obscuring the origin of API calls; and people located in U.S.-sanctioned countries may not use the platform. Keep one stable exit per researcher and key, stay inside your limits, and treat the proxy as a route — not a change of who you are.
Scroll horizontally with the arrow keys to read all content.
| Criterion | Choose | Why |
|---|---|---|
| Product | Rotating residential proxy | A household IP in the country you choose |
| Billing | By traffic, Premium or Budget line | Collection pages and API replies are light; pay per GB used |
| How many endpoints | One per researcher and API key | Each key always calls through the same endpoint |
| Country | Where OpenSea loads and you are allowed to use it | Nothing is preselected for Web3 — choose before you generate |
| Protocol | HTTP (preselected) or SOCKS5 | HTTP works in browsers, Python and curl |
| IP changes | Sticky in the chosen country — leave Global rotation off | For one fixed IP all day, choose static ISP |
The “Configure OpenSea proxies” button opens rotating residential proxies for the Web3 use case, billed by traffic. Buy traffic for the line you choose, then pick the region before you generate.
Scroll horizontally with the arrow keys to read all content.
| Criterion | Static ISP | Rotating residential | Datacenter |
|---|---|---|---|
| What you get | A home-broadband IP fixed to you for the whole term | Household IPs: a sticky session in the country you pick, or rotation on the Budget line | Fixed IPs in data centres — the console's fastest and cheapest option |
| Price | Per IP and term, shown in PTC before you pay (1 PTC = US$1) | Per GB: Budget US$1.50, Premium US$5.00, from 1 GB | Per IP and term, shown in PTC before you pay |
| Best for OpenSea | Signed-in collection management and listing work on one fixed IP | Reading collections and stats from blocked networks, paid per GB | A server that reads the API around the clock within your key's limits |
Prices in US dollars; you pay with PTC credit (1 PTC = US$1). Top up your wallet, then buy the line you need. Auto-renew isn't available yet, so renew static IPs in My assets before their term ends.
The “Configure OpenSea proxies” button opens Rotating Residential Proxies with the Web3 use case selected. Choose the Line, then under Traffic allowance click Add traffic and buy a package or enter Custom GB. Under Connection settings keep Exit mode at Choose region / sticky IP, pick the Region and Protocol, and click Review cost and generate.
Expected result Your configuration lists By traffic, Web3, Choose region / sticky IP and the region.
After payment the console opens My assets. Choose View credentials on the new proxy and copy the endpoint (host:port), username and password.
In your OpenSea account open Settings > Developer, verify your email and create a key, stating your real use. Send it in the X-API-KEY header on every request.
Call the collection stats endpoint through the proxy, as in the example below, and keep each key on its own exit. In a browser, open opensea.io in a profile that uses the same proxy.
Expected result The script prints the floor, owners, sales and volume for the collection.
Scroll horizontally with the arrow keys to read all content.
# pip install requests
import requests
PROXY = "http://USERNAME:PASSWORD@HOST:PORT" # residential endpoint from My assets
PROXIES = {"http": PROXY, "https": PROXY}
API_KEY = "YOUR_OPENSEA_API_KEY"
SLUG = "doodles-official" # collection slug from the OpenSea URL
r = requests.get(f"https://api.opensea.io/api/v2/collections/{SLUG}/stats",
headers={"X-API-KEY": API_KEY}, proxies=PROXIES, timeout=30)
r.raise_for_status()
total = r.json()["total"]
print("floor:", total["floor_price"], total["floor_price_symbol"])
print("owners:", total["num_owners"], "sales:", total["sales"])
print("volume:", total["volume"], total["volume_symbol"])
Reads a collection's floor, owners, sales and volume. Read floor_price with floor_price_symbol and volume with volume_symbol — they can be in different currencies — and keep each API key on one exit.
Check Is the key in the X-API-KEY header, and has an instant free-tier key passed its seven days?
Fix Create a full key under Settings > Developer and send it in the header.
Check How close are you to the limits in the response headers?
Fix Slow down and cache results. Don't spread one job over several IPs — OpenSea's terms prohibit it.
Check Does ipinfo.io in the same browser show an exit abroad? On a mainland China network, is the Proxy302 Helper running?
Fix Fix the browser's proxy or start the Helper and reload; complete any security check in the browser.
No. Here a proxy is a network exit — the IP your traffic leaves from. Proxy contracts are a smart-contract pattern and have nothing to do with how you connect to OpenSea.
No. OpenSea's terms prohibit using multiple IP addresses against its rate limits or traffic filters. Stay within your key's limits; full keys get higher limits than instant free-tier keys.
OpenSea's API terms prohibit obscuring the origin of API calls and say nothing specific about proxies. Keep each key on one exit — a static IP if the job runs all day — state your real use when you create the key, and ask OpenSea first if you're not sure your setup fits.
It gives you a route where your network blocks the site. It doesn't change OpenSea's eligibility rules: people located in U.S.-sanctioned countries, or under sanctions themselves, may not use it.
Instant free-tier keys work for seven days with low limits. For ongoing research create a full key under Settings > Developer — up to three per account.
Rotating residential in sticky mode for reading public collections and stats; static ISP for signed-in collection management or listing work on one fixed IP.
Third-party source · Checked:
Read on 2026-10-18: opensea.io was blocked in its last test (2026-06-14) and hasn't been tested since; api.opensea.io sits under the same blocked domain; magiceden.io was blocked (2026-08-11); blur.io connected in its latest conclusive test.
Independent connection tests; individual networks can differ.
Third-party source · Checked:
Aggregated web_connectivity results through the public OONI API on 2026-10-18: 30 of 31 measurements confirmed blocked by a block page, 1 more anomalous.
Volunteer measurements; individual networks can differ.
Official documentation · Checked:
Section 3: you may not use the platform if you are located in, ordinarily resident in or organized under the laws of a U.S.-sanctioned country, or are subject to sanctions. Section 8: not to circumvent access controls, rate limits or traffic filters by using unauthorized tools, multiple IP addresses or obfuscating traffic sources. Section 10 (API terms): not to obscure the origin of API calls. The terms do not mention proxies or VPNs.
Official documentation · Checked:
Send the key in the X-API-KEY header; instant free-tier keys come from POST https://api.opensea.io/api/v2/auth/keys and expire after 7 days; full keys are created under Settings > Developer after email verification, up to three per account; limits are returned on key creation and in response headers.
Official documentation · Checked:
GET https://api.opensea.io/api/v2/collections/{slug}/stats with the x-api-key header; the response has total (floor_price, floor_price_symbol, num_owners, sales, volume, volume_symbol) and intervals.
Product observation · Checked:
Read in the console source on 2026-10-18: for the Web3 use case the rotating residential page bills by traffic on a Premium or Budget line (a prepaid package, or PTC wallet debit where your account offers it), starts in Choose region / sticky IP mode — a sticky session in the chosen country, not a permanently fixed IP — and allows Global rotation only on the Budget line with prepaid traffic. HTTP or SOCKS5; each generation creates one endpoint. Its Web3 note reads “Public information research: Actual traffic billing · HTTP CONNECT / SOCKS5 · choose region · respect service limits”.
Product observation · Checked:
Budget rotating residential US$1.50 per GB and Premium US$5.00 per GB, both from 1 GB; account credit in PTC at 1 PTC = US$1.00; static ISP and datacenter leases depend on region, quantity and term and are shown before you pay — as published on the pricing page (checked against the production catalogue on 2026-10-09).
Create an account, top up once and pick rotating residential, static ISP or datacenter. Rotating residential exits cover 195+ countries and regions.