Skip to content
SilphCo

API Getting Started

Authenticate and call the SilphCo Analytics REST API

Last updated:

On this page

Quick start

  1. Create an account and generate an API key at the dashboard.
  2. Send the key as a Bearer token on every request.
  3. Browse the interactive reference for parameters and response shapes.
curl -H "Authorization: Bearer YOUR_API_KEY" \
  "https://silphcoanalytics.xyz/api/v3/cards?limit=1"

Authentication

All /api/v3 data routes require Authorization: Bearer YOUR_API_KEY. Requests without a valid key return HTTP 401.

Check daily usage with GET /keys/usage using the same Bearer token.

Endpoints

Base URL: https://silphcoanalytics.xyz/api/v3

Analytics

MethodPathDescription
GET/api/v3/analytics/grade-premiumGrade premium analytics
GET/api/v3/analytics/kfactorShare k-factor metrics

Cards

MethodPathDescription
GET/api/v3/cardsList and filter cards
GET/api/v3/cards/summaryCard summary rollup
GET/api/v3/cards/timeseriesMulti-card time series
GET/api/v3/cards/{id}Card detail
GET/api/v3/cards/{id}/analyticsCard analytics
GET/api/v3/cards/{id}/market-historyDaily market history
GET/api/v3/cards/{id}/physical-salesPhysical marketplace sales
GET/api/v3/cards/{id}/price-historyPrice history
GET/api/v3/cards/{id}/salesOn-chain sales for one card
GET/api/v3/cards/{id}/vwapVolume-weighted average price
POST/api/v3/cards/analytics/batchBatch card analytics
POST/api/v3/cards/batchBatch card lookup

Market

MethodPathDescription
GET/api/v3/market/volumeMarket-wide volume by set

Search

MethodPathDescription
GET/api/v3/lookupResolve a card or set identifier
GET/api/v3/populations/searchSearch graded populations
GET/api/v3/searchFull-text card search
GET/api/v3/trendingTrending cards leaderboard

Sets

MethodPathDescription
GET/api/v3/setsList sets
GET/api/v3/sets/{id}Set detail
GET/api/v3/sets/{id}/breakdownSet sales breakdown
GET/api/v3/sets/{id}/populationSet population report
GET/api/v3/sets/{id}/price-distributionSet price distribution
GET/api/v3/sets/{id}/trending-cardsTrending cards in a set
GET/api/v3/sets/{id}/volume-historySet volume over time

Unavailable routes

These routes appear in contract metadata or older docs but are not callable on the public API. Use the replacement where listed.

RouteStatusUse instead
GET /api/v3/cards/{id}/price_historyRemovedUse `GET /api/v3/cards/{id}?include=price_history`.
GET /api/v3/marketplacesNot availableNot exposed on the public API.
GET /api/v3/salesNot availableUse `GET /api/v3/cards/{id}/sales` for per-card sales.
POST /api/v3/events/shareNot availableNot exposed on the public API.

Response envelope

Every v3 response uses silphco-envelope.v1. The payload lives in data; the contract field names its schema version.

Pagination

Lists accept offset and limit (max 200). Per-card sales use an opaque next_cursor.

Errors

Errors return contract: "error.v1" with error.code and error.message. HTTP 401 indicates a missing or invalid key; 404 means the resource or route does not exist on the public API.

Examples

# Search
curl -H "Authorization: Bearer YOUR_API_KEY" \
  "https://silphcoanalytics.xyz/api/v3/search?q=charizard&limit=5"

# Card detail with price history
curl -H "Authorization: Bearer YOUR_API_KEY" \
  "https://silphcoanalytics.xyz/api/v3/cards/base1-4?include=price_history"

# Market volume (30 days)
curl -H "Authorization: Bearer YOUR_API_KEY" \
  "https://silphcoanalytics.xyz/api/v3/market/volume?days=30&language=en"

Reference