Knowledge Base
  • 💡Welcome To PointPay
  • 📃WhitePapper v 1.0
    • Disclaimer
    • Market Overview
      • Overview of 2018-2023
      • Evolution and Statement
      • Challenges and Opportunities
    • PointPay 2.0
      • Ecosystem Overview
      • Services Synergy
    • Crypto Exchange
      • Main Benefits
      • Security Measures
      • Customer Support
    • Digital Vault
      • Role in Ecosystem
      • Features and Benefits
      • Integration with other Services
    • PointPay Token
      • Token Info
      • Utility and Benefits
    • Project Future
      • Project Vision
      • Upcoming Features
    • Conclusion
  • 📈Tokenomics
  • ⚖️Token Swap Flow
  • 🔗Network
    • Mainnet&TestNet
    • Smart contracts
      • Contract Deployment
      • Deploy with Remix IDE
      • Deploy with Thirdweb
    • Explorer API
    • RPC API
  • Exchange API Documentation
    • Public endpoints | HTTP
      • Pairs List
      • Pairs Stats
      • Specific Pair Stats
      • Order Book Data
      • Market History
      • Market History Data
      • Products
      • Symbols
      • Depth List
      • Chart Data KLine
    • Private endpoints | HTTP
      • Authentication and API Keys
      • Create Limit Order
      • Cancel Order
      • My Active Orders
      • All My Trade Balances
      • My Specific Trade Balance
      • My Order Info
      • My Trades Info
      • My Order History
      • My Order History List
    • Basic structure | WEBSOKET
    • Public methods | WEBSOKET
      • Ping-Pong
      • System Time
      • KLine methods
      • Market Price methods
      • Market Status methods
      • Deals methods
      • Depth methods
    • Private methods | WEBSOKET
      • Authorization
      • My Assets methods
      • My Orders methods
Powered by GitBook
On this page
  • Details
  • With Authentication
  1. Exchange API Documentation
  2. Public endpoints | HTTP

Pairs List

This method returns the list of all public pairs available on PointPay Exchange.

Details

GET https://api.pointpay.io/api/v1/public/markets

CURL Example
curl -X GET "https://api.pointpay.io/api/v1/public/markets" -H "accept: application/json"

Response parameters:

Name
Type
Description

name

STRING

Pair name

moneyPrec

NUMERIC

Precision of money currency

stock

STRING

Ticker of stock currency

money

STRING

Ticker of money currency

stockPrec

NUMERIC

Precision of stock currency

feePrec

NUMERIC

Precision of fee

minAmount

NUMERIC

Minimal amount of stock to trade

Response example:

{
    "code": 200,
    "success": true,
    "message": "",
    "result": [
        {
            "name": "SSV_USDT",
            "moneyPrec": 8,
            "stock": "SSV",
            "money": "USDT",
            "stockPrec": 8,
            "feePrec": 8,
            "minAmount": "0.001"
        },
        ...
  ]
}

Response example:

<html>

<head>
	<title>400 Bad Request</title>
</head>

<body>
	<center>
		<h1>400 Bad Request</h1>
	</center>
	<hr>
	<center>nginx</center>
</body>

</html>

This error occurs in the following cases:

  • Invalid URL

  • Request contains invalid headers

Response example:

{
    "timestamp": 1660766043722,
    "status": 404,
    "error": "Not Found",
    "message": "",
    "path": "/api/v1/public/markets-test"
}

This error occurs in the following cases:

  • The requested URL was not found

With Authentication

POST https://api.pointpay.io/api/v1/public/markets

Headers

Name
Type
Description

X-TXC-APIKEY*

STRING

X-TXC-PAYLOAD*

STRING

Сonverted Base64 string containing body JSON

X-TXC-SIGNATURE*

STRING

Encrypted HmacSHA512 string containing body JSON with a API secret key

Request Body

Name
Type
Description
Example

request*

STRING

A request path without the domain name

/api/v1/public/markets

nonce*

NUMERIC

A 13-character number that must always be greater than the nonce of the previous completed request (we suggest generating a nonce as the UNIX timestamp in milliseconds)

1704070810000

CURL Example
curl --location --request POST 'https://api.pointpay.io/api/v1/public/markets' \
--header 'Content-Type: application/json' \
--header 'X-TXC-APIKEY: 0000000000XXXXXXXXXXXXXXXXX' \
--header 'X-TXC-PAYLOAD: 0000000000XXXXXXXXXXXXXXXXX' \
--header 'X-TXC-SIGNATURE: 0000000000XXXXXXXXXXXXXXXXX' \
--data-raw '{"request":"/api/v1/public/markets","nonce":1704070810000}'

Response example:

{
    "code": 200,
    "success": true,
    "message": "",
    "result": [
        {
            "name": "SUSHI_BTC",
            "moneyPrec": 8,
            "stock": "SUSHI",
            "money": "BTC",
            "stockPrec": 8,
            "feePrec": 8,
            "minAmount": "0.001"
        },
        ...
    ]
}

Response example:

{
    "code": 400,
    "success": false,
    "message": "authentication failure",
    "result": []
}

This error occurs in the following cases:

  • The request was signed incorrectly.

  • Some of the provided parameters are incorrect.

  • The base URL or path is incorrect.

Response example:

{    
    "timestamp": 1727100900,
    "status": 404,
    "error": "Not Found",
    "message": "",
    "path": "/api/v1/public/public/test"
}

This error occurs in the following cases:

  • The request was made with undefined data and the service cannot find the data for response.

PreviousPublic endpoints | HTTPNextPairs Stats

Last updated 7 months ago

This public endpoint can also be used as a POST request with (similar to ) to allow you to access more data.

Public

Provided is incorrect or less than on previous completed request

The API keys are not .

authentication
private endpoints
nonce
activated
API key