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
  1. Exchange API Documentation
  2. Private endpoints | HTTP

Create Limit Order

This method is used to create a Limit Order with the specified parameters. If successful, returns information about the placed order.

Details

POST https://api.pointpay.io/api/v1/order/new

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

market*

STRING

Any public pair

BTC_USDT

price*

STRING

Order price (in 2nd ticker of pair)

60000

amount*

STRING

Order amount (in 1st ticker of pair)

0.1

side*

STRING

sell or buy

buy

request*

STRING

A request path without the domain name

/api/v1/order/new

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/order/new' \
--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/order/new","market":"BTC_USDT","price":"60000","amount":"0.1","side":"buy","nonce":1704070810000}'

Response parameters:

Name
Type
Description

orderId

NUMERIC

Order ID

market

STRING

Order pair

side

STRING

Order side (buy / sell)

type

STRING

Order type

timestamp

NUMERIC

Order creation time

price

STRING

Order price

dealMoney

STRING

Executed order amount (in 2nd ticker of pair)

dealStock

STRING

Executed order amount (in 1st ticker of pair)

amount

STRING

Order amount (in 1st ticker of pair)

takerFee

STRING

Order taker fee

makerFee

STRING

Order maker fee

left

STRING

Available order amount (if = 0 means finished order)

Response example:

{
    "code": 200,
    "success": true,
    "message": "",
    "result": {
        "orderId": 1040149431,
        "market": "BTC_USDT",
        "side": "buy",
        "type": "limit",
        "timestamp": 1727085860.026000,
        "price": "60000",
        "dealMoney": "0",
        "dealStock": "0",
        "amount": "0.1",
        "takerFee": "0.000425",
        "makerFee": "0.000425",
        "left": "0.1"
    }
}

Response example 1:

{
    "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 2:

{
   "code":400,
   "success":false,
   "message":"operation blocked",
   "result":[]
}

This error occurs in the following cases:

  • Order creation is not available currently for the requested pair.

Response example 3:

{
    "code": 400,
    "success": false,
    "message": "invalid input",
    "result": []
}

This error occurs in the following cases:

  • One or more body params provided incorrectly

  • Required body params are not provided

Response example:

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

This error occurs in the following cases:

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

PreviousAuthentication and API KeysNextCancel Order

Last updated 7 months ago

Public

Provided is incorrect or less than on previous completed request

The API keys are not .

nonce
activated
API key