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 fair-values API

The fair-values API from River Markets — 2 operation(s) for fair-values.

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

This API exposes 3 operations across 2 paths, and defines 5 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.

3 operations 2 paths 5 schemas 1 DELETE1 GET1 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 fair-values 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 3

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

fair-values 3
GET
/v1/fair-values
List Fair Values
list_fair_values_v1_fair_values_get 2 params → 200422
POST
/v1/fair-values
Set Fair Value
set_fair_value_v1_fair_values_post body → 200422
DELETE
/v1/fair-values/{subaccount_id}/{river_id}
Delete Fair Value
delete_fair_value_v1_fair_values__subaccount_id___river_id__delete 2 params → 204422

Schemas 5

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

FairValueUpsert
object
Request schema for setting a fair value (insert-or-overwrite).
3 properties 3 required
FairValueResponse
object
A user-set fair value for one instrument on one subaccount.
4 properties 4 required
ValidationError
object
5 properties 3 required
FairValueListResponse
object
1 property 1 required
HTTPValidationError
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

river-markets-fair-values-api-openapi.yml Raw ↑

Other APIs River Markets publishes across the network.

River Markets balance API
River Markets complex-orders 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
River Markets watchlists API