Upload Collection Content


Creating a collection is only the first step to using the power of Aspen APIs to power your NFT dreams. Next up, you'll need to get your media type and emboss them on the blockchain as tokens and single NFTs. This section of the docs will direct creators to the API endpoints that provide the ability to just this, with all the edge cases that may crop up. We welcome you to a thorough guide on how to create NFTs within your collection.

Step 1: Creating an NFT token

When building your request to the Create a new token endpoint, you'll need to provide the following fields:

collectionId an integer value that comes from the response of the Create Collection endpoint. This integer is important.
name The name of your collection
description A description of your collection
externalURL A URL for hosting your collection media if you choose not to host on IPFS. This can be left blank.
numberOfFiles the number of files this particular NFT will have. Aspen has rich support for 721 and 1155 standards, so we welcome you to choose any number of files for this key-value pair.

A 200 response body should have some interesting key-value pairs, but the most essential three for uploading our NFTs are:

  • id
  • Status
  • syncStatus

Step 2: Providing metadata

A POST request to the Upload Token Metadata endpoint is used for uploading, as URI, the essential properties of the NFT, ergo the name, traits, description, and other more granular information you want to associate with your token.

When building this request, all you will need is the

collectionId The token id number. This is an integer value that comes from the response of the Create a new token endpoint
JSONa JSON object of the metadata you want to send in

A 201 response body should return the metadata values

Step 3: Uploading files to the NFT token

Step 3: with the Post /token/{id}/files/{index} endpoint

The upload a file endpoint uploads the file to IPFS and returns a hash that is used to create the unique NFT. When building out this request, you'll need the

collectionId the token id number

and that should be all