Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

River Markets orders API

Place and manage orders on prediction market exchanges.

River Markets orders API is one of 13 APIs that River Markets publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include orders. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 7 operations across 4 paths, and defines 15 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against a single base URL, https://api.rivermarkets.com.

7 operations 4 paths 15 schemas 1 DELETE3 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.rivermarkets.com
Authentication
API Key, API Key, API Key, HTTP Bearer
License
Proprietary
Resource Areas
1

Authentication & Security 4

River Markets orders API declares 4 security schemes for authenticating requests. An API key is passed in the header as X-River-Key-Id (SignedRequestKeyId). An API key is passed in the header as X-River-Timestamp (SignedRequestTimestamp). An API key is passed in the header as X-River-Signature (SignedRequestSignature). It accepts HTTP bearer tokens (BearerAuth). By default, every request must be authenticated.

  • SignedRequestKeyId — UUID of your API key (from Settings → API Keys).
  • SignedRequestTimestamp — Current unix seconds. Must be within 30s of server time.
  • SignedRequestSignature — Base64 Ed25519 signature over the canonical request: METHOD\nPATH\nSORTEDQUERY\nTIMESTAMP\nSHA256(body) hex. See /api-reference/authentication for the full rec…
  • BearerAuth — JWT bearer token for web client authentication.

Paths & Operations 7

Across 4 paths, the API surfaces 7 operations — 1 DELETE, 3 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

orders 7

Place and manage orders on prediction market exchanges.

POST
/v1/orders
Create Order
create_order_v1_orders_post body → 202422
GET
/v1/orders
List Orders
list_orders_v1_orders_get 12 params → 200422
GET
/v1/orders/{order_id}
Get Order
get_order_v1_orders__order_id__get 1 param → 200422
DELETE
/v1/orders/{order_id}
Cancel Order
cancel_order_v1_orders__order_id__delete 1 param → 202422
PATCH
/v1/orders/{order_id}
Edit Order
edit_order_v1_orders__order_id__patch 1 param body → 202422
GET
/v1/orders/{order_id}/queue-position
Get Order Queue Position
get_order_queue_position_v1_orders__order_id__queue_position_get 1 param → 200422
POST
/v1/orders/cancel-all
Cancel All Orders
cancel_all_orders_v1_orders_cancel_all_post body → 202422

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are OrderDetailResponse (24 properties), OrderResponse (23 properties), OrderCreate (12 properties), OrderFillResponse (9 properties). Each schema is shown below with its type and property counts.

OrderCreate
object
Schema for creating a new order.
12 properties 5 required
OrderListResponse
object
Schema for list of orders.
2 properties 2 required
OrderCreateResponse
object
Schema for order create response.
2 properties 2 required
CancelAllRequest
object
Request body for cancelling all orders for a subaccount.
2 properties 1 required
OrderQueuePositionResponse
object
Schema for the queue-position response of an order.
3 properties 3 required
CancelOrderResponse
object
Schema for cancel order response
2 properties 2 required
ValidationError
object
5 properties 3 required
OrderEditResponse
object
Schema for order edit response.
2 properties 2 required
TriggerOrder
object
The order that will be sent to the exchange when the conditional order's condition is met. For TP/SL: the parent order fills → the conditional activates → this…
5 properties 3 required
OrderFillResponse
object
Schema for a single fill on an order.
9 properties 9 required
OrderResponse
object
Schema for order response, when user request information about an order.
23 properties 10 required
OrderDetailResponse
object
Schema for order detail response including fills.
24 properties 10 required
OrderEditRequest
object
Schema for editing (amending) an existing simple limit order. qty is the TOTAL order quantity (not remaining) — matches Kalshi's amend semantics. At least one…
2 properties
ConditionalOrderCreate
object
Schema for a conditional order (take profit or stop loss) attached to a parent order.
5 properties 2 required
HTTPValidationError
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

river-markets-orders-api-openapi.yml Raw ↑

Other APIs River Markets publishes across the network.

River Markets balance API
River Markets complex-orders API
River Markets fair-values API
River Markets fills API
River Markets generic-assets API
River Markets markets API
River Markets orderbooks API
River Markets positions API
River Markets prices API
River Markets subaccounts API
River Markets tradeprints API
River Markets watchlists API