LogoLogo
ProductsCommunityGitHubShare Feedback
NFT Kit
NFT Kit
  • What is the NFT KIT?
    • Introduction
    • Non-Fungible Tokens (NFTs)
      • NFT | Basics
      • Technologies & Concepts
    • NFT Kit
      • NFT Kit | Basics
        • Overview
        • Functionality
      • NFT Flavors & Ecosystems
      • Architecture
        • Low-Level Service Abstraction
        • Ecosystem Abstraction
        • High-Level Interfaces / APIs
      • Use Cases
  • Getting started
    • Quick Start
  • Ecosystems
    • Ethereum | Polygon | Shimmer
      • Setup
      • NFT | Creation & Management
        • Smart Contract Deployment
        • Minting NFTs
        • Get NFT Metadata
        • Get Account Balance
        • Get Token Owner
        • Get Collection Info
        • Get NFTs by Account
      • NFT | Ownership Verification
        • Ownership Verification
        • Ownership Verification With Traits
      • Smart Contract | Extensions
        • Pausable
        • Burnable
      • Smart Contract | Access Control
        • Ownership
        • Role-Based Access Control
    • Ocean Protocol
      • Setup
      • NFT | Verification
      • NFT | Wallet
      • Architecture
    • Tezos
      • Architecture
      • NFT | Creation & Management
        • Smart Contract
        • Add Minter
        • NFT Minting
        • Fetch NFT metadata
        • Get account NFTs
        • Get contract metadata
      • NFT | Ownership Verification
        • NFT Ownership Verification
        • NFT Ownership Verification Within A Collection
        • NFT Ownership Verification With Traits
      • NFT | Wallet
      • Tutorials
        • Minting NFTs on Tezos
          • Setup
          • New Collection
          • First NFT
          • Verification
          • Wallet
    • Near Protocol
      • Architecture
        • Smart Contract
        • Blockchain NFTs operations
        • NFTs Queries
      • NFT | Creation & Management
        • NEAR Sub-Account
        • Deploy NFT Contract
        • NFT | Minting
      • Querying NFT information controller
        • Get NFTs for account
        • Get NFT By Token Id
        • Get NFT contract metadata
      • NFT | Wallet
      • Tutorials
        • Minting NFT on Near Protocol
          • Near Wallet Creation
          • Setup NFT-Kit
          • Create Sub-account
          • Smart Contract ( Collection )
          • Minting your first NFT
        • NFT Ownership Verification
        • Wallet
    • Polkadot
      • Architecture
      • Query NFTs
        • Unique network
          • Fetching Token id & Collection id
          • Fetching NFT metadata
        • Parachain Networks
          • Fetching Tokens by subscan
          • Fetching EVM ERC721 Collectibles by subscan
      • NFT | Ownership Verification
        • NFT ownership verification
        • NFT ownership verification within a collection
        • NFT ownership verification with traits
      • NFT | Wallet
        • Polkadot parachains
        • Polkadot EVM compatible parachains
    • Flow
      • Architecture
        • Cadence Scripts
        • NFT Operations (FCL)
      • Querying NFT information Controller
        • Get NFTs for an account
        • Get NFTs in Collection
        • Get NFT by Token Id
      • NFT | Ownership Verification
        • NFT ownership verification on Flow
        • NFT ownership verification in collection on Flow
      • NFT | Wallet
        • Flow Blockchain
    • Algorand
      • Architecture
        • Algorand Standard Assets (ASAs)
      • NFT | Creation & Management
        • Account Creation
        • NFT Creation (ARC3)
      • Querying Asset information
        • Get Assets for account
        • Get Asset Details
        • Get NFT Metadata by asset id
        • Get NFT by Asset id
      • NFT | Ownership Verification
        • NFT ownership verification
        • NFT ownership verification with traits
        • NFT ownership verification Based on Creator
        • NFT Metadata verification against a dynamic policy
      • NFT | Wallet
        • Algorand Blockchain
    • IPFS
  • Concepts
    • Soulbound Tokens (SBTs)
    • NFT verification with OPA
  • Configurations
    • Configuration Files
    • Gas Provider
  • Community
    • Discord
    • Twitter
    • Newsletter
    • GitHub Discussions
  • DEVELOPER RELATIONS
    • Roadmap
    • Contribute
    • Share Feedback
    • Contact
  • Product Editions
    • Open Source | Always Free
    • Enterprise | Self-Managed
    • Cloud Platform | Managed
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Ecosystems
  2. Near Protocol
  3. NFT | Creation & Management

NFT | Minting

Minting an NFT on a blockchain allows the creator to prove ownership and authenticity of the digital asset

Mint NFT

API Doc

Swagger Doc | ReDoc

Curl call example

curl -X POST "http://0.0.0.0:7000/v2/nftkit/nft/near/chain/{chain}/contract/{contract_id}/mint"
-H  "Content-Type: application/json"
-d  "{"account_id": "string","token_id": "string","title": "string","description": "string","media": "string","media_hash": "string","reference": "string","reference_hash": "string","receiver_id": "string"}"

Path parameters:

  • chain:[string] chain to work with. Either testnet or mainnet .

  • contract_id:[string] smart contract account .

Body parameters:

{
  "account_id": "string",
  "token_id": "string",
  "title": "string",
  "description": "string",
  "media": "string",
  "media_hash": "string",
  "reference": "string",
  "reference_hash": "string",
  "receiver_id": "string"
}
  • account_id: Your account id.

  • token_id: The token ID , must be unique.

  • title: The name of this specific token.

  • description: A longer description of the token.

  • media: URL to associated media. Preferably to decentralized, content-addressed storage.

  • media_hash : The base64-encoded sha256 hash of content referenced by the media field. This is to guard against off-chain tampering.

  • reference : URL to an off-chain JSON file with more info.

  • reference_hash : Base64-encoded sha256 hash of JSON from reference field. Required if reference is included.

  • receiver_id: The account that's receiving the token.

Example:

curl -X POST "http://0.0.0.0:7000/v2/nftkit/nft/near/chain/testnet/contract/nft.waltid.testnet/mint"
-H  "Content-Type: application/json"
-d  "{"account_id": "waltid.testnet","token_id": "0","title": "Walt.id NFT Art","description": "Waltid NFT Kit Example","media": "https://avatars.githubusercontent.com/u/84637756","media_hash": "","reference": "","reference_hash": "","receiver_id": "nft.waltid.testnet"}"
val accountId = "waltid.testnet"
val contractId =  "nft.waltid.testnet"
val receiverId = "waltid.testnet"
val chain = "testnet"


val result = NearNftService.mintNftToken(
        account_id = accountId,
        contract_id = contractId,
        token_id = "1",
        title = "waltid",
        description = "My NFT",
        media = "https://waltid.net",
        media_hash = "",
        reference = "",
        reference_hash = "",
        receiver_id = receiverId,
        chain = chain,
        
    )
println("operation result: $result")

PreviousDeploy NFT ContractNextQuerying NFT information controller

Last updated 2 years ago

Was this helpful?