FRUITS API Document
  • FRUITS API Document
  • Java sample code
  • PHP sample code
  • Creating Unsigned Transactions
  • Create Transaction Request
  • Create Transaction Response
  • SERVER INFORMATION
    • Get Blockchain Status
    • Get My Info
    • Get State
    • Get Time
  • ACCOUNT
    • Get Account
    • Get Account Blocks
    • Get Balance
    • Send FRTS
    • Send FRTS Multi
    • Set Account Info
  • TRANSACTION
    • Broadcast Transaction
    • Calculate Full Hash
    • Get Transaction
  • BLOCK
    • Get Block
    • Get Block Id
    • Get Blocks
  • Process flowchart
    • FRTS, token send/receive flow
    • FRUITS Wallet connect flow
  • Create & Active Account
    • Coding Guidelines in Java
    • Coding Guidelines in JS
  • FRUITS Node API For Single NFT
    • Create NFT Smart Contract
    • Mint NFT
    • Transfer NFT
    • Place a sell order
    • Cancel a sell order
    • Buy NFT
    • Get NFT By URI
    • Get List of NFTs by Account
    • Get List of NFTs for sale
    • Get List of NFTs By Smart Contract
  • FRUITS Node API For multiple NFT
    • Create NFT Smart Contract
    • Mint NFT
    • Transfer NFT
    • Place a sell order
    • Cancel a sell order
    • Buy NFT
    • Get Multiple Token By Account
    • Get Multiple Token By Contract
    • Get Multiple Token By Owners
    • Get Multiple Token By Uri
Powered by GitBook
On this page

FRUITS API Document

The FRUITS API allows interaction with FRUITS nodes using HTTP requests to port 8126. Most HTTP requests can use either the GET or POST methods, but some API calls accept only the POST method for security reasons. Responses are returned as JSON objects.

The JSON response fields are each preceded by one of the following: S for ‘string’, A for ‘array’, O for ‘object’, N for ‘number’, or B for ‘boolean’. Note: This is a documentation convention only. These notations are not part of the API responses. In the examples, the FRUITS node is represented as localhost and requests and responses are formatted for easy reading; line breaks and spaces are not used except in some parameter values. All requests are in URL format, which implies the HTTP GET method. When GET is allowed, the URL can be entered into a browser URL field, but proper URL encoding is usually required (e.g., spaces in a parameter value must be replaced by + or %20). Otherwise, the URL should be used as a guide to preparing an HTTP POST request using cURL.

NextJava sample code

Last updated 1 year ago