This is a fully automated solution that allows you to deploy an NFT with a single API call to the [Polygon Matic](https://polygon.technology/) blockchain ( this a layer 2 Ethereum network). Features: - Jobs are placed in a resilient redis queue. - Deploy a smart contract for each collection - Uploads base64 data to [IPFS](https://ipfs.io/) (The InterPlanetary File System) - Create the NFT Json Metadata and include the [IPFS](https://ipfs.io/) results in it, as specified by your custom path. (Internally is done by [lodash _.set](https://lodash.com/docs/4.17.15#set)) - Upload the compiled NFT Json Metadata to [IPFS](https://ipfs.io/) - Deploy the NFT to the blockchain - Use a web hook to notify you of the stages and status of the job. Because of the nature of these networks and technology. There are multiple failure points related to network congestion, timeouts, incompletion, or erroneous results either on Blockchain or the [IPFS](https://ipfs.io/) . That is why we set up a resilience work queue, which attempts each step until the NFT is successfully deployed. To ensure that the NFT is deployed, jobs are retried 10 times until the error status is marked as unrecoverable. ---------------------------------------------- Use this endpoint to deploy and NFT. This is a fully automated solution 🤖🧞 that allows you to deploy an NFT with a single API call to the [Polygon Matic](https://polygon.technology/) blockchain ( this is a layer 2 Ethereum network). Other blockchains will be added in the future ( BSC, CELO, ONE). Please review the JSON Schema for this endpoint. 🛑To use this endpoint, you must first [claim Collection Contracts](#post-claim-collection-contracts)🛑 ### Payload Properties 💣💥 - 🔸 nftMintOrder Type: `object` | `⛑ required`

_This defines the NFT Collection - Blockchain, collection name, royalties, symbol, and the Unique NFT Token id; this information is used to identify the order in the system._ This schema does not accept additional properties.

**_Properties:::_** - 🔸 sendAddress Type: `string` | `⛑ required`

_During the Mint phase, the NFT will be sent to this address. This will be the NFT's owner._

- 🔸 blockchain Type: `string` | `⛑ required`

_At the moment, only Polygon MATIC is supported. Other blockchains will be integrated in the future ( BSC, CELO, ONE)._

The value is restricted to the following: 1. _"MATIC"_

- 🔸 tokenId Type: `string` | `⛑ required`

_Token ID that will be issued. This identifies the NFT within the collection._

The value must match this pattern: `^[0-9]{1,32}$`

- 🔸 collectionName Type: `string` | `⛑ required`

_Name of the collection_

- 🔸 symbol Type: `string` | `⛑ required`

_The collection's symbol. For example, the Bitcoin symbol is BTC._

The value must match this pattern: `^[a-zA-Z0-9_-]{1,30}$`

- 🔸 royalties Type: `array`

_At the moment, Opensea does not support split revenue. When a splitter address is implemented or our NFT Marketplace contract becomes accessible, this information will be used. This project will earn a split revenue of 2.5%._

- **_Items_** Type: `object`

This schema does not accept additional properties.

**_Properties:::_**

- 🔸 address Type: `string` | `⛑ required`

_Address where royalties should be sent every transaction_

- 🔸 splitRoyaltyRate Type: `number` | `⛑ required`

_Percentage for this Address_

- 🔸 webhooks Type: `object`

_Webhook for each stage of the redis job status - For further information and structure, see the Webhooks Section._

This schema does not accept additional properties.

**_Properties:::_** - 🔸 completed Type: `string` | `⛑ required`

_This is triggered when the NFT is successfully minted._

- 🔸 progress Type: `string`

_This is triggered when job update the status of the order/job_

- 🔸 failed Type: `string`

_This is triggered when a task fails. Please keep in mind that the job is retrying 10 times until the order's status is declared as unrecoverable. Fatal Error_

- 🔸 unrecoverableFatalError Type: `string`

_This is triggered when a job fails many times and will not be retried; the job is then removed from the queue stack._

- 🔸 uploadIpfsFiles Type: `array`

_A collection of base64 data to be uploaded to the IPFS. Also, assign each file result to the NFT Metadata Path._

This schema does not accept additional items.

- **_Items_** Type: `object`

This schema does not accept additional properties.

**_Properties:::_** - 🔸 base64data Type: `string` | `⛑ required`

_Base 64 data will be uploaded to the IPFS._

- 🔸 setMetadataPath Type: `string` | `⛑ required`

_The upload result will be set to JSON NFT Metadata obj, specify by this Path, which is done internally by [lodash _.set](https://lodash.com/docs/4.17.15#set)_