🔐
Trust Enterprises
  • Getting Started
  • Intro video course
    • Introduction of the Trust Enterprises project [2:16]
    • Deployment of your first Serverless client [6:29]
    • Using Postman with the Trust Enterprises API [6:33]
    • Installation of the Trust Enterprises Laravel package [7:51]
    • Basic interaction with your client with Laravel. [10:28]
  • Deployment
    • Vercel
    • Environment Variables
    • Github Actions
  • REST API
    • Overview
    • Inscriptions
      • Deploy an Inscription
      • Mint an Inscription
      • Burn an Inscription
      • Transfer an Inscription
    • NFT Ecosystem
      • Create an NFT Collection
      • Generate Metadata
      • Mint an NFT
      • Transfer an NFT
      • Claiming NFTs through Passes
    • Accounts
    • Tokens
      • Create a token
      • Bequesting a token
      • Token Holdings and Balance
    • Topics
      • Get topic info
      • Creating a new topic
      • Updating a topic
    • Consensus Messages
    • Balance
    • Status
    • Webhooks
  • The Laravel Client
    • Overview
    • Installation
    • Interacting with your client
    • Create a Marketplace
    • Manage your Inscription Flow
    • Checking account balances and sending tokens
  • Contributing
    • Local Development
      • Architecture Rationale
    • Contributing Guidelines
    • Changelog
  • Links
    • Github
    • Trust Enterprises
    • Postman Documentation
    • Hedera Network Status
    • Remote Software Development
Powered by GitBook
On this page

Was this helpful?

  1. REST API
  2. Tokens

Create a token

Create a token with a name, symbol, supply, and memo.

Create new token

POST https://hedera-serverless-consensus.vercel.app/api/token

This endpoint allows you to create a token with a name, symbol, supply, and memo.

The memo is an important feature to allow linking but not exclusive to: Hedera Topic IDs (dynamic NFTs), decentralised identity (DIDs), or IPFS (dStorage) images/files.

Headers

Name
Type
Description

Authentication*

string

The API_SECRET_KEY from th e client's environment variables.

Request Body

Name
Type
Description

symbol*

String

Symbol of the token

name*

String

Name of the token

supply*

Number

Number of tokens to mint, whole.

memo

String

Attached memo to a token, for linking to external content or for dynamic NFT purposes.

decimals

int

decimals of the token, if not present will default to 6.

{
    "data": {
        "name": "Matt token",
        "symbol": "MATT",
        "memo": "abc",
        "reference": "basic.fungible",
        "supply": "100",
        "supplyWithDecimals": "100000000",
        "tokenId": "0.0.2839273"
    }
}
PreviousTokensNextBequesting a token

Last updated 2 years ago

Was this helpful?