OPopensea
Collection Endpoints

Upload collection page media

Changed on

Upload an image or an MP4 video for the collection page: the hero (8:3 on desktop, 16:9 on mobile), about, narrative, content block and team sections. Set the content_type query parameter to the exact MIME type of the file. Video must be video/mp4. Files can be up to 50 MB. This response starts a three-step upload flow. First, request this context from OpenSea. Second, call the returned method at the returned URL. For POST, add every fields entry unchanged as a multipart text field, then add a file part containing the bytes. The file part must be last. Let the HTTP library generate the multipart boundary; do not set the overall multipart Content-Type header yourself. POST storage uploads normally return 204. For PUT, upload the raw bytes, use only headers explicitly required by the endpoint, and expect 200. Treat any 2xx storage response as success. The URL and fields are short-lived sensitive credentials. Do not log, persist, alter, or put them in tickets. Third, after storage succeeds, pass the returned token to the documented OpenSea API endpoint. Do not use the token before the storage upload succeeds. Pass the token in PATCH /api/v2/collections/{slug}/metadata as { image: { token } } for an image or { video: { token } } for a video. The media type must match the upload: a video token sent as image, or the reverse, does not resolve and the metadata update fails with 400 without saving anything. The placement picks where the file is stored, but the token is accepted in any media field of the metadata update. The presigned upload expires about a minute after it is issued.

post/api/v2/collections/{slug}/media/{placement}

Request

Path parameters

slugstring required

Collection slug

placementstring required

Where the media goes on the page: hero_desktop, hero_mobile, about_preview, about_section, overview (narrative and content block media), overview_background (narrative backgrounds) or team.

Query parameters

content_typestring required

Exact MIME type of the file: any image type (image/png, image/jpeg, image/gif, image/webp and so on) or video/mp4.

Response

Upload context generated successfully

fieldsobject required

Short-lived sensitive multipart text fields for POST. Submit every entry unchanged before the file part. Content-Type contains the exact MIME type required by the signed policy. This map is empty for PUT.

method'POST' | 'PUT' required

HTTP method to use at url. Current upload contexts use POST.

tokenstring required

Reference for the next OpenSea API call. Use it only after storage returns 2xx.

urlstring required

Short-lived storage URL. Use it exactly as returned and treat it as sensitive.

Example response

{
  "fields": {
    "key": "uploads/example.png",
    "Content-Type": "image/png"
  },
  "method": "POST",
  "token": "upload-token-example",
  "url": "https://uploads.example.com/"
}

Changes