Developer API
REST v1CryptoJam market data through a REST API.
Cryptocurrencies
USD prices, market capitalization and trading volumes.
/api/v1/developer/coinsRequest parameters
| Parameter | Type | Description |
|---|---|---|
page | integer | Page number, from 1 |
pageSize | integer | Number of results, 1–250 |
search | string | Coin name or symbol |
sort | string | rank, price, marketCap, volume24h, change24h |
order | string | asc or desc |
Response fields and pagination
Responses contain data and meta. Main fields: id, slug, name, symbol, rank, priceUsd, change24h, marketCapUsd, volume24h, updatedAt and source. An unavailable price is null. The default page size is 50. Symbols are not unique: use id or slug.
Price history
Stored quotes for a specific cryptocurrency.
/api/v1/developer/history/{slug}Request parameters
| Parameter | Type | Description |
|---|---|---|
range | string | 24h, 7d, 30d, 90d, 1y, all, max |
from / to | string | Custom range, ISO 8601 |
granularity | string | 1d or tick |
History coverage and sources
Each point contains timestamp, priceUsd and available additional metrics. Dates use UTC. The all range means the entire locally stored history; its beginning may differ from the coin's launch date.
Check meta.coverageStart, meta.coverageEnd, meta.source, meta.gaps, meta.truncated and meta.isDemo. Request smaller intervals for truncated responses. USD and USDT quotes are stored separately.
About market dataAuthorization and request example
Send your key in the X-API-Key header. Keep it on your application's server.
curl -H "X-API-Key: YOUR_API_KEY" \
"https://cryptojam.net/api/v1/developer/history/bitcoin?range=30d"My API keys
Sign in to create a key
Manage access to market and historical data.
Continue with emailAccess and limits
Access restrictedData delivery is currently disabled. Requests return 503; keys can still be created.
Access details and errors
Data delivery is enabled after the providers' redistribution rights are confirmed. CoinGecko is the default permitted provider. Coin Metrics Community data are excluded from the developer API.
Daily quotas use UTC. The limit and remaining requests are shown in X-RateLimit-Limit and X-RateLimit-Remaining.
- 400
- Invalid parameters
- 401
- Key missing or invalid
- 403
- Insufficient permissions
- 404
- Resource not found
- 429
- Request limit exceeded
- 503
- Data unavailable
Errors contain code and message inside an error object. After a 429 response, follow the Retry-After header when present.