Developers

REST APIOrders

Remove orders by hash

POST
/orders/remove-by-hash

Remove orders from the orderbook by their hash for the authenticated signer (max 100). This will not cancel the order on-chain. Requires JWT or project 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

Remove orders by hash request

data*

Remove orders by hash request data

Response Body

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

Response for POST /v1/orders/remove

success*boolean
removed*array<string>

Orders that were successfully removed

noop*array<string>

Orders that were not removed because they were already filled, removed or cancelled

rejected*array<string>

Orders whose removal was rejected because they are still within their market's removal lock window. These may be retried after the order's removal lock expires.

Example Request
curl -X POST 'https://api.predict.fun/v1/orders/remove-by-hash' \  -H 'Content-Type: application/json; charset=utf-8' \  -d '{  "data": {    "hashes": [      "string"    ]  }}'
Example Response
{  "success": true,  "removed": [    "string"  ],  "noop": [    "string"  ],  "rejected": [    "string"  ]}

Remove orders POST

Remove orders from the orderbook for the authenticated signer (max 100). This will not cancel the order on-chain. Requires JWT or project authentication.

Get connected account GET

Get information for the connected user account. points are for one season, season or the current season by default. Requires JWT authentication.