OpenSea API Keys

OpenSea API keys let Zyper use OpenSea’s authenticated marketplace and mint endpoints. They are separate from your RPC endpoints: an RPC connects Zyper to the blockchain, while an OpenSea key connects supported features to OpenSea.

What uses an OpenSea API key#

Zyper uses the keys in OS API for supported features including:

• the OpenSea API mint method when it is available for a drop;
• creating and cancelling NFT listings;
• loading offers and accepting WETH offers;
• OpenSea marketplace data and activity in NFT tools; and
• marketplace enrichment for PnL.

Not every task needs a key. If a feature explicitly says that an OpenSea API key is required, add and test one before relying on that feature during a live drop.

Open the OS API manager#

Select OS API in the Zyper sidebar. Keys are stored in the dedicated encrypted local key store. The table masks each key during normal use; Show All and Copy reveal the selected values only when you request them.

Create groups to organise keys by OpenSea account or purpose. For example, you could keep long-lived developer keys separate from short-lived instant keys.

Add existing keys#

1. Create or select a group.
2. Click Add Keys.
3. Paste one OpenSea API key per line. Blank lines and lines beginning with # are ignored.
4. Click Verify & Add.

Zyper verifies every manually imported key with OpenSea before saving it. Invalid and duplicate keys are rejected instead of entering the active key pool.

Get an OpenSea API key#

You have three options:

Instant key#

Run the built-in OpenSea Instant Key social module. It creates a free-tier key without an OpenSea account, wallet, email, or social profile and stores it in the Instant group. OpenSea currently makes instant keys expire after seven days and gives them lower rate limits, so check the expiry shown in OS API before a drop.

Developer key through Zyper#

Run the built-in OpenSea Developer Key social module. This uses a selected account’s OpenSea developer flow, completes email verification through its connected Google session or Gmail app password, waits for approval, and stores the issued key in the encrypted Generated group.

Developer key through OpenSea#

Request a key from the official OpenSea developer settings, then import it into OS API. OpenSea’s current application flow requires a verified email plus organization, website, and intended-use details. See the official API key guide for the latest requirements.

Test keys and read their status#

Click Test on one key or Test All for the active group. A successful test shows latency and the returned rate-limit balance. The expiry column shows the known lifetime for keys created by Zyper; manually imported keys may show Unknown when OpenSea does not expose their expiry to the test request.

Status	What to do
invalid	Replace or delete the rejected key.
error	Check your connection and retry; the test may have failed before OpenSea could validate the key.
Expiring	Generate or import a replacement before the displayed expiry.
Expired	Delete it after adding a working replacement.
Low remaining quota	Reduce unnecessary requests or switch to another eligible account/key pool.

OpenSea rate limits are shared by keys under the same OpenSea account. Creating several keys on one account does not multiply that account’s allowance. Keys from separate accounts may have separate limits, but you must still follow OpenSea’s current terms and rate-limit rules.

Using multiple keys#

Zyper keeps all valid keys in the managed pool and can distribute supported OpenSea requests across them. Groups are for organisation; deleting a key or an entire group removes those keys from the pool immediately.

For scheduled OpenSea tasks, Settings → OpenSea Early Start can request mint data repeatedly during the final second before launch. This can consume quota quickly across a large task group, so test your keys and watch their remaining allowance before enabling it.

Keep keys private#

• Never post an OpenSea API key in Discord, screenshots, logs, or support tickets.
• Use Show All or Copy only when necessary, then clear any plaintext copy you saved elsewhere.
• If a key is exposed, revoke or replace it through OpenSea and delete the old value from Zyper.
• When asking for support, send the masked key row, status, app version, and the time of the failed test—not the full key.