waves_logo Docs
  • Node Owner Guide
    Node Owner Guide
  • Install Waves Node
    • Deploy Node in Docker
      Deploy Node in Docker
    • Install Node on Ubuntu
      Install Node on Ubuntu
    • Install Node on macOS
      Install Node on macOS
    • Install Node on Windows
      Install Node on Windows
    • Install from Source (Building SBT)
      Install from Source (Building SBT)
    • Deploy Node in Cloud
      • Deploy Node in Yandex.Cloud
        Deploy Node in Yandex.Cloud
      Deploy Node in Cloud
    Install Waves Node
  • Synchronize Waves Blockchain
    • Import/Export Blockchain
      Import/Export Blockchain
    • Download the Latest Blockchain
      Download the Latest Blockchain
    • Rollback Waves Node
      Rollback Waves Node
    Synchronize Waves Blockchain
  • Upgrade Waves Node
    Upgrade Waves Node
  • Node Configuration
    Node Configuration
  • Logging Configuration
    Logging Configuration
  • Node Wallet
    Node Wallet
  • Features
    • Activation protocol
      Activation protocol
    Features
  • Custom Blockchain
    Custom Blockchain
  • Node REST API
    • API Key
      API Key
    • Working with Transactions
      Working with Transactions
    • Monetary Fields
      Monetary Fields
    • Pagination
      Pagination
    • CORS
      CORS
    • API Limitations of Pool of Public Nodes
      API Limitations of Pool of Public Nodes
    • Response Codes and Errors
      Response Codes and Errors
    Node REST API
  • Extensions
    • gRPC Server
      gRPC Server
    • Blockchain Updates
      Blockchain Updates
    Extensions
  • Troubleshooting
    • Block Generation FAQ
      Block Generation FAQ
    Troubleshooting
  • Node Go
    Node Go
      • English
      • Русский
      On this page
      waves_logo Docs

          # Monetary Fields Format

          By default, monetary values are represented in API responses as numbers. These numbers can take up to 64 bit that can cause issues with programming languages that represent integers with fewer than 64 bit, such as JavaScript. To work around these issues, you can obtain monetary values as strings by specifying the following HTTP header in the request:

          Accept: application/json; large-significand-format=string
          

          Example:

          curl -X GET --header 'Accept: application/json;large-significand-format=string' 'https://nodes.wavesnodes.com/blocks/headers/last'
          

          Below is the list of endpoints accepting this header:

          • GET /addresses/balance/{address}/{confirmations}

            Field: balance.

          • GET /addresses/balance/details/{address}

            Fields: regular, generating, available, effective.

          • GET /addresses/effectiveBalance/{address}/{confirmations}

            Field: balance.

          • GET /addresses/effectiveBalance/{address}

            Field: balance.

          • GET /addresses/balance/{address}

            Field: balance.

          • GET /blocks/headers/last

            Fields: reward, totalFee.

          • GET /blocks/headers/at/{height}

            Fields: reward, totalFee.

          • GET /blocks/headers/seq/{from}/{to}

            Fields: reward, totalFee.

          • GET /blocks/at/{height}

            Fields: reward, fee, amount, sellMatcherFee, price, matcherFee, buyMatcherFee, totalAmount, totalFee.

          • GET /blocks/signature/{signature}

            Fields: reward, fee, amount, sellMatcherFee, price, matcherFee, buyMatcherFee, totalAmount, totalFee.

          • GET /blocks/address/{address}/{from}/{to}

            Fields: reward, fee, amount, sellMatcherFee, price, matcherFee, buyMatcherFee, totalAmount, totalFee.

          • GET /blocks/last

            Fields: reward, fee, amount, sellMatcherFee, price, matcherFee, buyMatcherFee, totalAmount, totalFee.

          • GET /blocks/seq/{from}/{to}

            Fields: reward, fee, amount, sellMatcherFee, price, matcherFee, buyMatcherFee, totalAmount, totalFee.

          • GET /blockchain/rewards/{height}

            Fields: totalWavesAmount, currentReward, minIncrement.

          • GET /blockchain/rewards

            Fields: totalWavesAmount, currentReward, minIncrement.

          • POST /transactions/calculateFee

            Field: feeAmount.

          • GET /transactions/info/{id}

            Fields: fee, amount, sellMatcherFee, price, matcherFee, buyMatcherFee, totalAmount.

          • GET /transactions/unconfirmed/info/{id}

            Fields: fee, amount, sellMatcherFee, price, matcherFee, buyMatcherFee, totalAmount.

          • GET /transactions/address/{address}/limit/{limit}

            Fields: fee, amount, sellMatcherFee, price, matcherFee, buyMatcherFee, totalAmount.

          • POST /transactions/broadcast

            Fields: fee, amount, sellMatcherFee, price, matcherFee, buyMatcherFee, totalAmount.

          • GET /transactions/unconfirmed

            Fields: fee, amount, sellMatcherFee, price, matcherFee, buyMatcherFee, totalAmount.

          • GET /assets/balance/{address}

            Fields: balance, minSponsoredAssetFee, sponsorBalance, quantity, fee

          • GET /assets/nft/{address}/limit/{limit}

            Fields: balance, minSponsoredAssetFee, sponsorBalance, quantity, fee

          • GET /assets/{assetId}/distribution/{height}/limit/{limit}

            Field: asset ID.

          • GET /assets/details/{assetId}

            Field: quantity.

          • GET /assets/balance/{address}/{assetId}

            Field: balance.

          • GET /consensus/generatingbalance/{address}

            Field: balance.

          • GET /debug/balances/history/{address}

            Field: balance.

          • GET /debug/stateChanges/info/{id}

            Field: fee.

          • GET /debug/stateChanges/address/{address}/limit/{limit}

            Fields: fee, amount, sellMatcherFee, price, matcherFee, buyMatcherFee, totalAmount.

          • GET /debug/portfolios/{address}

            Fields: balance, in, out.

          Working with Transactions
          Pagination
          Working with Transactions
          Pagination