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 tradeprints API

Recent trades for a market. Pairs with the /v1/ws/tradeprints WebSocket for live updates.

River Markets tradeprints 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 tradeprints. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 1 operation across 1 path, and defines 6 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.

1 operations 1 paths 6 schemas 1 GET

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 tradeprints 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 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

tradeprints 1

Recent trades for a market. Pairs with the /v1/ws/tradeprints WebSocket for live updates.

GET
/v1/tradeprints
Get Tradeprints
get_tradeprints_v1_tradeprints_get 2 params → 200422

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are TradeprintEvent (5 properties), ValidationError (5 properties), TradeprintsResponse (4 properties), HTTPValidationError (1 property). Each schema is shown below with its type and property counts.

TradeprintsBulkResponse
object
Response for GET /v1/tradeprints?riverids=.... results preserves the order of the requested riverids. Partial failures are surfaced per-row (status notfound) w…
1 property
HTTPValidationError
object
1 property
ValidationError
object
5 properties 3 required
TradeprintEvent
object
A single trade print. aggressorbuyflag is true when the aggressing (taker) side bought — i.e. the trade hit an ask. The frontend renders side color and "Buy/Se…
5 properties 2 required
TradeprintsResponse
object
Per-market block of recent trades from the exchange.
4 properties 1 required
TradeprintsStatus
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

river-markets-tradeprints-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 orders API
River Markets positions API
River Markets prices API
River Markets subaccounts API
River Markets watchlists API