Skip to main content
GET
/
payment
/
open
/
institution
/
v1
/
pay
/
convert
/
currency
Query Available Convert Currencies
curl --request GET \
  --url https://openplatform.gateapi.io/payment/open/institution/v1/pay/convert/currency \
  --header 'X-GatePay-Certificate-ClientId: <x-gatepay-certificate-clientid>' \
  --header 'X-GatePay-Nonce: <x-gatepay-nonce>' \
  --header 'X-GatePay-On-Behalf-Of: <x-gatepay-on-behalf-of>' \
  --header 'X-GatePay-Signature: <x-gatepay-signature>' \
  --header 'X-GatePay-Timestamp: <x-gatepay-timestamp>'
{
  "status": "SUCCESS",
  "code": "000000",
  "errorMessage": "",
  "data": {
    "currency": [
      "USDT",
      "GT",
      "HOOK",
      "ETH",
      "DOT",
      "BTC",
      "DAL",
      "LTC",
      "COS",
      "POL",
      "SOL",
      "DOGE",
      "ALGO",
      "STPT",
      "BCH",
      "SHIB"
    ]
  }
}

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 /payment/open/institution/v1/pay/convert/currency endpoint. The full schema, parameters, and examples are rendered from the linked OpenAPI definition above.

Notes

Headers

X-GatePay-Certificate-ClientId
string
required

Merchant client ID assigned when registering the application

Example:

"mZ96D37oKk-HrWJc"

X-GatePay-Signature
string
required

Request signature for verification

Example:

"8504fe097f7297f8952c76e628ce59dbc93d1df64c95f26c73140ef365d4aa1471826ada0534315461682ec35c131d7e133c51d2ab0822fe7366650a111887ba"

X-GatePay-Timestamp
string
required

UTC timestamp in milliseconds

Example:

"1740019013818"

X-GatePay-Nonce
string
required

Random string, recommended length within 32 characters

Example:

"9722139164"

X-GatePay-On-Behalf-Of
string
required

Required delegated-subject header. Provide the initiating account ID for this request. For institution merchant APIs, this is typically the target sub-account ID; for institution charge and transfer APIs, it can be either an institution account ID or a sub-account ID.

Query Parameters

side
enum<string>

Trade direction ("buy" or "sell")

Available options:
buy,
sell
Example:

"sell"

Response

200 - application/json

Success

status
string

SUCCESS or FAIL

code
string

Error code

errorMessage
string

Error message

data
object