🔐
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

Accounts

Create a hedera account for a user, this will provide you will the capability to send tokens to a user.

Create new account

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

This endpoint allows you to create a user, you can then link the response accountId to an actor you have in your system.

You'll also receive an encryptedKey and publicKey, that you should store in your database.

The encryptedKey can be decrypted with your API_SECRET_KEY.

Headers

Name
Type
Description

Authentication*

string

The API_SECRET_KEY from th e client's environment variables.

{
    "data": {
        "accountId": "0.0.2838629",
        "encryptedKey": "4cc0ccd5446023a2:4e584643658b020a8b2fbfeceb293e00fdaf6cb41bdc3438379e6f6acbc4efeb516320e82b1d9102594f975f4b6ef8444f960017611035598297defb26b19b08a34e8f366639ee72bb265567b7f585597fd459eedfa8c1c6e40e68f439efff9a18f2ccd71cee260ea0f125c4aad730e2",
        "publicKey": "302a300506032b6570032100cebb39dbfc486ec10e6c415233f12572e2abd3d1ac3687308f1953deaef92643"
    }
}
PreviousClaiming NFTs through PassesNextTokens

Last updated 3 years ago

Was this helpful?