Skip to main content
GET
/
v1
/
pay
/
fixedaddress
/
chains
Query Supported Networks and Currencies
curl --request GET \
  --url https://openplatform.gateapi.io/v1/pay/fixedaddress/chains \
  --header 'X-GatePay-Certificate-ClientId: <x-gatepay-certificate-clientid>' \
  --header 'X-GatePay-Nonce: <x-gatepay-nonce>' \
  --header 'X-GatePay-Signature: <x-gatepay-signature>' \
  --header 'X-GatePay-Timestamp: <x-gatepay-timestamp>'
{
  "status": "SUCCESS",
  "code": "000000",
  "errorMessage": "",
  "data": {
    "Chains": [
      {
        "chain": "ETH",
        "showChainNameEn": "ETH/ERC20",
        "currencies": [
          "USDT",
          "DAI",
          "ETH",
          "MATIC",
          "USDC"
        ]
      },
      {
        "chain": "TRX",
        "showChainNameEn": "Tron/TRC20",
        "currencies": [
          "USDT"
        ]
      }
    ]
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.gate.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

This page documents the GET /v1/pay/fixedaddress/chains endpoint. The full schema, parameters, and examples are rendered from the linked OpenAPI definition above. Queries the networks and currencies supported by GatePay for static address collection.

​
Notes

Headers

​
X-GatePay-Certificate-ClientId
string
required

The clientId assigned when the merchant registers an application in the Gate merchant console.

Example:

"4186d0c6-6a35-55a9-8dc6-5312769dbff8"

​
X-GatePay-Signature
string
required

Request signature. GatePay uses this signature to verify whether the request is valid.

​
X-GatePay-Timestamp
string
required

UTC timestamp in milliseconds when the request is generated. GatePay will not process requests where the difference from the receive time exceeds 10 seconds.

Example:

"1672905655498"

​
X-GatePay-Nonce
string
required

Random string. Must comply with HTTP header rules; recommended length is within 32 characters, composed of digits and letters.

Example:

"9578"

Response

200 - application/json

Successful response

​
status
enum<string>

Response status

Available options:
SUCCESS,
FAIL
Example:

"SUCCESS"

​
code
string

Response code

​
errorMessage
string

Error description

​
data
object