How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

River Markets subaccounts API

Manage trading subaccounts. Each subaccount can have its own exchange credentials and positions.

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

This API exposes 5 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

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

5 operations 2 paths 6 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.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 subaccounts 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 5

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

subaccounts 5

Manage trading subaccounts. Each subaccount can have its own exchange credentials and positions.

GET
/v1/subaccounts
List Subaccounts
list_subaccounts_v1_subaccounts_get → 200
POST
/v1/subaccounts
Create Subaccount
create_subaccount_v1_subaccounts_post body → 201422
GET
/v1/subaccounts/{subaccount_id}
Get Subaccount
get_subaccount_v1_subaccounts__subaccount_id__get 1 param → 200422
PATCH
/v1/subaccounts/{subaccount_id}
Update Subaccount
update_subaccount_v1_subaccounts__subaccount_id__patch 1 param body → 200422
DELETE
/v1/subaccounts/{subaccount_id}
Delete Subaccount
delete_subaccount_v1_subaccounts__subaccount_id__delete 1 param → 204422

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are SubaccountResponse (6 properties), ValidationError (5 properties), SubaccountCreate (3 properties), SubaccountUpdate (2 properties). Each schema is shown below with its type and property counts.

HTTPValidationError
object
1 property
ValidationError
object
5 properties 3 required
SubaccountCreate
object
Schema for creating a new subaccount.
3 properties 1 required
SubaccountResponse
object
Schema for subaccount response.
6 properties 5 required
AccountType
string
Type of trading subaccount.
SubaccountUpdate
object
Schema for updating a subaccount.
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

river-markets-subaccounts-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 tradeprints API
River Markets watchlists API
Where this information came from

This is an independent, third-party profile of River Markets subaccounts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.