Overview

The FullNode HTTP API is the primary service offered by Pollux nodes, enabling users to interact with the blockchain by sending transactions. The process typically involves the following three steps:

Create a Transaction: Use system contract APIs to generate the transaction.

Sign the Transaction: Sign the transaction using the SDK.

Broadcast the Transaction: Send the transaction to the network using the BroadcastTransaction endpoint.

To differentiate between HEX and Base58check addresses, the visible parameter is introduced. Additionally, the Permission_id parameter is used to specify the type of permission for multi-signature transactions.

Note: When using the HTTP API, both GET and POST methods are supported for data requests. If using the POST method, parameters must be passed in the HTTP message body in JSON format.

📘Note
Although Pollux has mitigated XSS risks by setting the Content-Type of HTTP APIs to application/json, a few APIs lack input validation. To better protect user data security, we strongly recommend encoding any data obtained from the APIs before displaying it in any UI, especially when the parameter visible = true is enabled by default.
A typical XSS protection method involves encoding all data received from the APIs for use in HTML. Use methods such as encodeURIComponent() or escape() to encode the data, which will convert special characters into their HTML entities and prevent them from being interpreted as HTML code by the browser.
Ensure proper implementation of XSS protection for all data from the APIs to guarantee user data security. For more information about XSS protection, it is recommended to refer to the following resources: OWASP XSS Prevention Cheat Sheet.

Full Node HTTP API

Overview#

Overview