Unlocking 180-Day Price History: Deeper Data, Cleaner Payloads

We are officially unlocking up to 180 days of price history for all cards.

The New Parameter: `priceHistoryDuration` #

To support longer timeframes without bloating our JSON responses with rigid field names like priceHistory90d or priceHistory180d, we are streamlining how we return this data.

There is now a single source of truth: the priceHistory array. By default, this returns 7 days of data. To reach back further, simply add the priceHistoryDuration parameter to your request.

GET Request Example:

GET /cards?game=mtg&priceHistoryDuration=180d

Supported Durations:

• 7d (Default)
• 30d
• 90d
• 180d

The API will dynamically populate the priceHistory field with the duration you requested. This keeps the response structure consistent regardless of the timeframe you are analyzing.

Deprecation Notice: `priceHistory30d` #

With the introduction of dynamic durations, the hardcoded priceHistory30d field is now redundant.

• Status: Deprecated.
• Behavior: Effective immediately, if you use the new priceHistoryDuration parameter in your request, the legacy priceHistory30d field will be automatically hidden from the response to keep the payload clean.
• Removal: The field will remain available for a short grace period for legacy calls, but will be removed entirely in the next major API update.

We recommend updating your integration to use priceHistoryDuration=30d as soon as possible.

A Quick Note on `casing_Inconsistency` #

While you are updating your parameters, you might notice something. You will see priceHistoryDuration (camelCase) sitting right next to include_statistics (snake_case) in our documentation.

We know.

It keeps us up at night, too. We are committed to standardizing this in API v2, but for now, please forgive the inconsistency. We blame the caffeine.

Ready to dig deeper? #

The 180-day history is live now. Check out the updated documentation to see the full response schema and start building better charts for your users today.