With authentication done, the next series of APIs interacted with are the Collection APIs. These APIs will allow you to create a collection, deploy the collection contract, upload the token metadata, get the deployment status of the collection and more.

To this end, understanding what data you will use in this section of the APIs is essential to understanding the power and utility our APIs provide. Let's dive in.

Selecting the Blockchain

Right now, Aspen allows creators to deploy their collections on testnet and mainnet. Mainnet options include Ethereum, Polygon, and Palm while their Testnet counterparts include Ropsten, Rinkeby, and Mumbai. This allows you, the creator, to have your tokens on testnet, see the power that we offer, and move to mainnet at your pace.


Creating a Collection is Better

In a new version of our APIs, we provide the ability for a developer to choose between the DropERC721 AND DropERC1155 contract types with the chain key.

While building out the Create Collection request body, the value used for the key/value pair of chain is important as this defines the blockchain that the collection and tokens will be minted on.

Take a look at a sample request for the create a collection endpoint.

  "name": "string",
  "symbol": "string",
  "chain": "Ethereum",
  "maxTokens": 0,
  "defaultLockTime": 3600,
  "royaltyPercentage": 0,
  "feeRecipientAddress": "string",
  "mintingWalletAddress": "string",
  "mintType": "PreMint",
  "limitMaxClaim": true,
  "maxClaimPerWallet": 0,
  "clientWallet": "string",
  "userTermsMessage": "string"

FIles per NFT

Every collection powered by Aspen naturally evolves to have a token, and here at Aspen, we support the ethereum standards ERC-721 and ERC-1155. While the 721 tokens are the foundation for non-fungible tokens and allow for 1:1 NFTs, 1155s are the future as they support non-fungible and semi-fungible tokens. What this means for your collection is that you can mix and match files inside one Token. The applications for this go from P2E gaming to music NFTs to everything else. The limits are endless, and Aspen is ready to power is all. To begin this journey, use the create a new token endpoint to choose the number of files you want in your token.

Take a look at a sample request for the create a new token endpoint.

  "collectionId": 0,
  "name": "string",
  "description": "string",
  "externalUrl": "string",
  "numberOfFiles": 2147483647

Ethereum Standards

Earlier in this section, we spoke about the ERC standards of 721 and 1155. Now, we're going to speak about how this choice impacts on your new collection and the benefits it has for you.

The ERC-721 standard is the foundation for the non-fungible tokens, as it allows for creating one-off tokens on the blockchain. Dapper Labs introduced the standard, and they used it to launch the beginnings of Cryptokitties, a series of collectibles that are one-off, non-fungible, and with a ownership history that can be checked on the blockchain. Essentially one asset per NFT per smart contract - 1:1:1. The ERC-1155 standard was the next step. Introduced by the Enjin Project, it allows for multiple assets on the same contract - what has been called "batch transfers". The 1155 standard also allows for semi and non-fungible tokens on the same contract. For creators and collectors, this means that an address can hold one-off assets and semi-fungible ones. A veritable practical application can be found in the P2E field, where semi-fungible in-game assets are traded on unique NFTs.