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

The watchlists API from River Markets — 4 operation(s) for watchlists.

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

This API exposes 8 operations across 4 paths, and defines 11 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.

8 operations 4 paths 11 schemas 2 DELETE2 GET1 PATCH2 POST1 PUT

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 watchlists 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 8

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

watchlists 8
GET
/v1/watchlists
List Watchlists
list_watchlists_v1_watchlists_get 1 param → 200422
POST
/v1/watchlists
Create Watchlist
create_watchlist_v1_watchlists_post body → 201422
GET
/v1/watchlists/{watchlist_id}
Get Watchlist
get_watchlist_v1_watchlists__watchlist_id__get 1 param → 200422
PATCH
/v1/watchlists/{watchlist_id}
Update Watchlist
update_watchlist_v1_watchlists__watchlist_id__patch 1 param body → 200422
DELETE
/v1/watchlists/{watchlist_id}
Delete Watchlist
delete_watchlist_v1_watchlists__watchlist_id__delete 1 param → 204422
POST
/v1/watchlists/{watchlist_id}/members
Add Watchlist Members
add_watchlist_members_v1_watchlists__watchlist_id__members_post 1 param body → 200422
DELETE
/v1/watchlists/{watchlist_id}/members
Remove Watchlist Members
remove_watchlist_members_v1_watchlists__watchlist_id__members_delete 1 param body → 204422
PUT
/v1/watchlists/{watchlist_id}/members/order
Reorder Watchlist Members
reorder_watchlist_members_v1_watchlists__watchlist_id__members_order_put 1 param body → 200422

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are MarketSearchResult (31 properties), WatchlistDetailResponse (7 properties), WatchlistResponse (6 properties), ValidationError (5 properties). Each schema is shown below with its type and property counts.

WatchlistUpdate
object
Request schema for renaming / editing a watchlist.
2 properties
WatchlistListResponse
object
1 property 1 required
WatchlistResponse
object
A watchlist summary (list view): metadata + ordered member riverids.
6 properties 5 required
HTTPValidationError
object
1 property
ValidationError
object
5 properties 3 required
WatchlistMemberReorder
object
Request schema for reordering a watchlist. The body is the full ordered list of riverids; the server rewrites position to match. Sending the whole array avoids…
1 property 1 required
WatchlistCreate
object
Request schema for creating a new watchlist.
4 properties 2 required
WatchlistDetailResponse
object
Response schema for a watchlist with its resolved members (detail view). members are ordered by position; riverids is the same ordering as a convenience for ha…
7 properties 6 required
InstrumentStatus
string
Instrument status derived in instruments table from exchange-specific fields. Kalshi: maps from kalshimarkets.status - 'active' - ACTIVE - everything else (clo…
MarketSearchResult
object
Schema for a single market search result.
31 properties 9 required
WatchlistMemberAdd
object
Request schema for adding members to a watchlist (appended at the end).
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

river-markets-watchlists-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 tradeprints API