Build transaction data for updating a SelfMint drop item
Changed onChanges an existing self-mint token's metadata and returns the ready-to-sign transaction that points the contract's base URI at the regenerated metadata. It does not change the token's supply. A token id that does not exist on the drop returns 404, and a drop that is not an ERC-1155 self-mint drop returns 400.
An ERC-1155 self-mint drop has no stages, publish step, or public mint. Each item is its own token id: saving one returns a transaction that creates it and mints its whole supply to the contract owner. The transaction's to is the drop's configurer contract (the one its getConfigurer() returns), not the drop contract, and it must be sent from from, the contract owner.
PATCH /api/v2/drops/{slug}/items/{token_id} takes the same body and saves the same metadata, but returns no transaction, so the contract keeps pointing at the old metadata. On a self-mint drop, use this endpoint and send its transaction.
Request
- Base URLhttps://api.opensea.io
- AuthAPI key in header x-api-key and OpenID Connect (https://auth.opensea.io/.well-known/openid-configuration, scopes: write:drops)
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
Collection slug
Drop item token id
Request body
Response
Ready-to-sign transaction data
Example response
{
"token_id": "1",
"value": "0"
}Changes
- info
added the new optional request property
- info
the request property
became nullable - info
the request property
became nullable - info
the request property
became nullable - info
added the media type
*/*for the response with the status - info
added the non-success response with the status
- info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status
- info