Set imageType to profile_picture for the avatar or banner_image for the profile banner. Set contentType to the exact MIME type of the image bytes; it must be an image type such as image/png, image/jpeg, image/gif or image/webp. Files can be up to 50 MB; the storage upload rejects a larger file or a non-image Content-Type field. 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/profile as profileImageToken for profile_picture or bannerImageToken for banner_image. Requires the write:profile scope.