REST APIOrders
Remove orders
Remove orders from the orderbook for the authenticated signer (max 100). This will not cancel the order on-chain. Requires JWT or project authentication.
ApiKeyAuthBearerAuthx-api-key<token>API key authentication via the x-api-key header.
AuthorizationBearer <JWT>Bearer authentication via the Authorization: Bearer <token> header.
application/json; charset=utf-8- body
Remove orders request
data*Remove orders request data
application/json; charset=utf-8- response
Response for POST /v1/orders/remove
success*booleanremoved*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.
curl -X POST 'https://api.predict.fun/v1/orders/remove' \ -H 'Content-Type: application/json; charset=utf-8' \ -d '{ "data": { "ids": [ "string" ] }}'{ "success": true, "removed": [ "string" ], "noop": [ "string" ], "rejected": [ "string" ]}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.
Remove orders by hash POST
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.