API Endpoints
OpenSea

Build creator fee enforcement transactions

post
https://api.opensea.io/api/v2/collections//creator_fee_enforcement

Build the transactions that turn creator fee enforcement on or off for a collection, for the owner to sign and send. Turning it on sets OpenSea's transfer validator on the contract (the Creator earnings tab in Studio); turning it off removes it. Nothing changes until the transactions are mined. Only the collection owner can call this, and the contract must be owned onchain by that wallet. When enforcement is already in the requested state, transactions is empty and there is nothing to send. Check the result with GET /api/v2/collections/{slug}/creator_fee_enforcement.

On chains that use the Limit Break V5 validator, set allow_eip7702_transfers, allow_smart_wallet_transfers or both to also get the policy update that lets those wallets send the collection's NFTs directly. It is one separate transaction to the transfer validator, sent after the one that sets it. For a collection that is already enforced, it is the only transaction returned. It rewrites the collection's whole policy as read when it was built, so request it right before signing.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

Collection slug

Body Params

Request body for turning creator fee enforcement on or off

boolean
Defaults to false

true also returns the Limit Break V5 policy update that lets EIP-7702 wallets (OpenSea embedded wallets, MetaMask Smart Accounts) send this collection's NFTs directly, which the V5 transfer validator rejects by default. Marketplace sales still pay creator earnings, but a 7702 wallet's delegate code could be written to settle a trade as a direct send, which skips them. When enforcement is already on, transactions holds only this update, or is empty when there is none to make (another validator, or a policy that already allows these sends). Ignored when enabled is false.

boolean
Defaults to false

true also returns the Limit Break V5 policy update that lets smart contract wallets (Safe, Coinbase Smart Wallet and other contract accounts) send this collection's NFTs directly, which the V5 transfer validator rejects by default. This is a wider opening than allow_eip7702_transfers: any contract holding the NFTs can then send them, including NFT AMM pools, whose swaps do not pay creator earnings. With allow_eip7702_transfers, both options go in one transaction. When enforcement is already on, transactions holds only the update, or is empty when there is none to make. Ignored when enabled is false.

boolean
required

true sets OpenSea's transfer validator on the contract so creator fees are enforced. false removes the validator.

Responses

401

Invalid or missing API key

500

Internal server error. Please open a support ticket so OpenSea can investigate.

Updated about 1 month ago

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
*/*

Updated about 1 month ago