Developers

REST APIOrders

Create an order

POST
/orders

Create a LIMIT or MARKET order for the authenticated user. Requires JWT authentication.

Authorization

ApiKeyAuthBearerAuth
headerx-api-key<token>

API key authentication via the x-api-key header.

headerAuthorizationBearer <JWT>

Bearer authentication via the Authorization: Bearer <token> header.

Request Body

application/json; charset=utf-8
  1. body

Create order request

data*

Create order request data

Response Body

Created

application/json; charset=utf-8
  1. response

Response for POST /v1/orders

success*boolean
data*

Create order response data

Example Request
curl -X POST 'https://api.predict.fun/v1/orders' \  -H 'Content-Type: application/json; charset=utf-8' \  -d '{  "data": {    "pricePerShare": "string",    "strategy": "MARKET",    "order": {      "salt": "string",      "maker": "string",      "signer": "string",      "taker": "string",      "tokenId": "string",      "makerAmount": "string",      "takerAmount": "string",      "expiration": 0,      "nonce": "string",      "feeRateBps": "string",      "side": 0,      "signatureType": 0    }  }}'
Example Response
{  "success": true,  "data": {    "code": "string",    "orderId": "string",    "orderHash": "string",    "removalLockedUntil": "string"  }}

Get orders GET

Get a list of your own orders with optional filters. Requires JWT authentication.

Get order match events GET

Get a paginated list of order match events with optional filtering. Results are sorted by executedAt DESC. The executedAfter and executedBefore filters are unix timestamps in milliseconds and both bounds are exclusive. The orderHashes filter accepts up to 25 order hashes, comma separated or repeated, and returns the match events in which any of those orders took part as maker or taker. Hashes that do not belong to any order are ignored. A match event describes a whole transaction, so filtering by a maker order also includes the other fills settled in the same transaction.