🔐
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

Bequesting a token

Send a token to an account that you have previously generated. This feature allows you to create decentralised experiences with onchain proof where a user requires no prior blockchain experience.

This feature is in beta and there will be unexpected side effects if the body parameters aren't used.

Send/bequest a token to an account

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

This endpoint allows you to send a token to user as a permissioned function, provide the encrypted keys and ids of the receiver and token.

Headers

Name
Type
Description

Authentication*

string

The API_SECRET_KEY from th e client's environment variables.

Request Body

Name
Type
Description

encrypted_receiver_key*

String

Encrypted private key of receiver

token_id*

String

ID of token to send

receiver_id*

String

Account id of receiving account

amount*

Number

amount of tokens to send

decimals

Number

Explicitly set decimals of the token

{
    "data": {
        "amount": "1",
        "receiver_id": "0.0.2120537",
        "transaction_id": "0.0.1156@1634128052.72220023"
    }
}
{
    "errors": [
        "\"encrypted_receiver_key\" length must be 241 characters long"
    ]
}
PreviousCreate a tokenNextToken Holdings and Balance

Last updated 2 years ago

Was this helpful?