With the following endpoint, you are able to upload a token and optional to also define placeholder values or also a complete metadata code for the metadata override.
Define the body for the request fitting for your token upload. Please remove the fields that don't apply for your upload. You have the option of uploading the file as BASE64 Content, URL Link, or IPFS Hash. If you submit Metadata, it will be used instead of the project's Metadatatemplate. You may submit either Metadata or MetadataPlaceholder, but not both.
For this example, we specified the body like that:
{"tokenname":"thetoken1","displayname":"The Token 1","description":"This is a test","previewImageNft": {"mimetype":"image/png","fileFromIPFS":"QmfA66piVcujJoSmL1fu1beJS2agvadXbzwv4hX4dnzqWY" },"subfiles": [ {"subfile": {"mimetype":"image/png","fileFromIPFS":"QmPep292dYH9CXH9AcMgbcEohXUc3P8ERbAfw7r9HM3AdY" } } ],"metadataPlaceholder": [ {"name":"background","value":"green" } ]}
Instead of giving the metadata via MetadataOverride, we used the metadataPlaceholder method to define custom fields. Please keep in mind that this placeholder method only works, if the custom fields are specified in the metadata template.
If you want to use the Metadata Override, please read here.
Using the Metadata Override instead of the Placeholder
In case you want to submit a complete 721 Metadata JSON, please keep in mint that you have to remove the MetadataPlaceholder fields in the request body and use the Metadata override field.
"metadataOverride": "string",
Continue to send your Curl as you would with the placeholder method, adding the escaped metadata to the field: