# Upload Event Media to an NFT Collection

Source: https://belong.net/blog/upload-event-media-to-an-nft-collection
Published: 2026-11-13T08:25:55.182Z
Updated: 2026-11-13T08:25:58.626Z

Learn how event organisers upload an NFT image and collection cover, validate ownership, and update collection metadata.

Upload Event Media to an NFT Collection

What it does

Belong CheckIn supports event media upload for organisers, developers, and authenticated collection owners who need to attach images or video to an NFT collection. The Media Upload Guide for MCP explains how to upload an NFT image and collection cover, verify ownership, update the collection media, and generate a contract URI for blockchain integration.

The capability is available through the MCP tool named add-collection-media and through the HTTP endpoint POST /media/:id/collection. Both routes attach media to an NFT collection identified by its collection ID. The documented flow accepts up to two files in total, and their order determines how each file is used.

The first file is the NFT image used for individual NFT display. The second is the collection cover image used for collection display. That order is part of the upload contract, so it should be decided before the files are sent.

For the HTTP route, each file can be up to 10MB. Supported MIME types are image/jpeg, image/png, image/webp, video/mp4, and video/webm. The MCP input uses base64-encoded media and can include an optional filename for each file.

After a successful upload, the response provides an array of media assets. Each asset can include its media ID, URL, MIME type, file size, image width and height, thumbnail URLs at several sizes, and a blurhash for image preview. This gives an integration the media details returned by the upload process.

How it works

- Set up authentication. Configure the MCP integration with an API key and make sure user authentication is available. The HTTP request also requires authentication.

- Identify the collection. Provide the NFT collection ID. With MCP, this is the id passed to add-collection-media. With HTTP, it is the :id path parameter in POST /media/:id/collection.

- Validate collection ownership. The process checks that the authenticated user owns the collection. A request from someone who is not the collection owner returns a 403 Forbidden response.

- Prepare the files in the required order. Put the NFT image first and the collection cover second. The MCP tool accepts an array containing base64 data and, optionally, a filename. The HTTP endpoint accepts files as form data.

- Stay within the upload limits. Send no more than two files in total. For HTTP uploads, keep each file within 10MB and use one of the documented image or video MIME types. Exceeding the total media count or supplying invalid files results in a bad request or an invalid-files error.

- Upload the media. Call add-collection-media through MCP or submit the form data to POST /media/:id/collection. The service uploads the files and attaches them to the specified NFT collection.

- Update the collection media. Once the files are uploaded, the documented process updates the collection media and its metadata. The flow then generates a contract URI for blockchain integration.

- Read the returned media assets. A successful response returns the attached media asset records. An integration can use the returned IDs, URLs, MIME types, dimensions, thumbnails, and blurhash values supplied in that response.

Who it's for and when to use it

This workflow is for event organisers and developers building with Belong CheckIn, as long as the authenticated user owns the NFT collection they want to update. It is useful when a collection needs both an image for individual NFT display and a cover for collection display.

Use the MCP route when the integration is already working with Model Context Protocol tools. The tool name is add-collection-media, and its file input is an array of base64-encoded media. Use the HTTP route when the integration needs to send file objects as form data to the collection media endpoint.

The two routes express the same important rules: the collection ID is required, the user must own the collection, no more than two files can be attached through this flow, and file order determines the display role. Choosing the route changes how the files are submitted, not what the first and second files represent.

The documented validation also makes the main failure cases explicit. Too many files produce a maximum-files error. A user who does not own the collection receives a forbidden response. Files that exceed 10MB or use an unsupported MIME type are invalid for the HTTP upload.

At the event

Consider an event organiser who is also the authenticated owner of an NFT collection. The organiser has one image intended for individual NFT display and another intended to represent the collection as its cover. Before uploading, the two files are placed in that exact order: NFT image first, collection cover second.

If the organiser's integration uses MCP, it calls add-collection-media with the collection ID and the base64-encoded files. If it uses HTTP, it appends both files to form data and posts them to the collection endpoint with authentication. Ownership is checked before the media is attached.

A successful response returns the media asset records. If the order is wrong, the files will not match the documented display roles. If more than two files are submitted, if a file exceeds 10MB, or if its MIME type is unsupported, the request does not meet the documented rules. If the authenticated user is not the owner, the request is forbidden.

Get started

Start with the Media Upload Guide for MCP. It contains the process flow, the add-collection-media input and output shapes, the HTTP endpoint, example requests, supported MIME types, upload limits, and documented errors.

Before sending media, confirm that the integration has an API key, user authentication is configured, the authenticated user owns the collection, and the files are ordered correctly. Developers can then choose the MCP tool or HTTP API according to how their integration submits files.

To access Belong CheckIn, visit checkin.belong.net.

FAQ

How many files can I upload to an NFT collection?

The documented flow allows no more than two files in total. The first is the NFT image for individual display, and the second is the collection cover.

Which file formats does the HTTP endpoint accept?

The endpoint supports JPEG, PNG, WebP, MP4, and WebM MIME types. Each uploaded file can be no larger than 10MB.

What happens if I do not own the collection?

Ownership is validated before media is attached. If the authenticated user is not the collection owner, the endpoint returns a 403 Forbidden response.
