Skip to main content
The RWA API provides the same published real-world asset data used by CoinStats. All seven endpoints require your X-API-KEY (or an OAuth Bearer token) and use https://api.coinstats.app as the base URL.

​
Find an asset

Use the returned rwaId, such as gold, for the detail, tokens, markets and asset-history endpoints. An RWA asset ID is distinct from a cryptocurrency coinId. The tokens endpoint returns a nullable CoinStats coinId, which can be used with the regular coin endpoints when a unique current mapping exists.

​
Filters and sorting

All endpoints accept currency, defaulting to USD. Use an uppercase supported code from /currencies. Monetary values are converted; percentages, quantities and timestamps are unchanged. Missing monetary values remain null. The three list endpoints accept page=1, limit=100 (maximum 100), literal case-insensitive search (up to 100 characters), sortBy and sortDirection=desc. Null values sort last in either direction. Use filter IDs returned in each response’s filters object. Market exchange uses CoinStats exchange IDs. Token id and market token use the token ID returned by the RWA response; this can differ from its CoinStats coinId. Markets include isAnomaly, row freshness and trade links. Spread and order-book depth are unavailable.

​
History

Aggregate and per-asset history have different range values:
Point timestamps use Unix milliseconds; update times use ISO 8601 strings. Aggregate history returns at most 500 sampled points. Per-asset history reports its resolution, available and availableFrom; missing metric observations are omitted and long ranges are sampled. Volume represents rolling 24h volume, so samples should not be summed to calculate traded volume over a range.

​
Availability and freshness

Responses preserve updatedAt and isStale. Detail sections and token/market lists also report available. A known asset awaiting enrichment can return prices while its metadata or markets are unavailable. An available empty list is a valid result. Null values remain null. Unknown assets return 404, invalid inputs return 400, unavailable publication or connection failures return 503, and request timeouts return 504. Server errors retain their upstream status and use the public API’s existing credit refund behavior.