Fanatical Product Feeds
This documentation describes the product feeds we publish for partners and affiliates. Every feed is regenerated automatically on a schedule (see each feed's page for cadence) and delivered as an HTTPs download.
If you're integrating for the first time, the rest of this page lists every available feed in a comparison table, along with the conventions that apply across all of them (region/currency model, conditional fields, bundle types). For day-to-day reference, jump straight to the page for the specific feed you're consuming.
About these docs
This documentation is generated directly from the Zod schemas in the feed-generation code. If a field is listed here, it is enforced at runtime.
Available Feeds
| Feed | Format | Regions |
|---|---|---|
| Minimal JSON Feed | application/jsonl | Global |
| Minimal JSON Feed (Regional) | application/jsonl | 8 Regions |
| Minimal CSV Feed | text/csv | Global |
| Minimal CSV Feed (Regional) | text/csv | 8 Regions |
| Extended JSON Feed | application/jsonl | Global |
| Extended JSON Feed (Regional) | application/jsonl | 8 Regions |
| Extended CSV Feed | text/csv | Global |
| Extended CSV Feed (Regional) | text/csv | 8 Regions |
| AWIN CSV Feed (Regional) | text/csv | 8 Regions |
| Legacy Affiliate Feed | application/jsonl (also gzipped) | Global |
Choosing a feed
We publish four shapes of the same underlying product data: minimal or extended, in JSON or CSV. Pick by what you need, in this order:
Minimal vs extended is the bigger decision. The minimal feed contains everything needed for listing pages, search results, and price comparison - names, URLs, prices, discounts, SKUs, platform info, and a short description. The extended feed adds full descriptions, multiple image sizes (XS through XL), category and feature tags, developer and publisher names, translated short descriptions, parent-product references for DLC and editions, and pre-rendered bundle marketing copy. If you only need to link to products with basic context, take the minimal feed - it's roughly half the size and updates more frequently. If you're building product detail pages, recommendation widgets, or anything that surfaces richer metadata, take the extended feed.
JSON vs CSV comes down to your tooling. JSON (specifically JSON Lines - one product per line) is the canonical shape: every field is preserved with its native type, nested objects like coupon and bundle_tiers stay structured, and translated descriptions appear as additional keys. The CSV variant is a flattened projection of the same data - nested objects become dot-notation columns (coupon.code, price.USD), array fields are joined inline, and a few JSON-only fields are omitted entirely (full bundle tier breakdowns, pre-rendered bundle copy, and parent/in_bundle references). If your pipeline goes straight into a spreadsheet, BI tool, or legacy ingestion script, CSV is usually faster to wire up. If you're loading into a database, data warehouse, or any code that benefits from typed fields, JSON is the better choice - and JSONL specifically is supported natively by BigQuery, Snowflake, Redshift, and most ETL tools.
Global vs regional is independent of the other choices. Every feed shape is published once globally (with included_regions per product and all relevant currencies on each price object) and again per supported country (with that country's currency only and included_regions omitted). If you serve a single market, the regional variant is smaller and easier to consume. If you serve multiple markets from one integration, take the global variant.
If you're still unsure, extended-json-regional is the most common starting point - full data, your region's currency, easy to subset later if you decide minimal is enough.
Authentication and access
All feeds are served from https://www.fanatical.com/feeds/ and require an API key. Contact affiliates@fanatical.com to request one - please include the name of your organisation, the integration you're building, and which feed(s) you plan to consume.
Once issued, pass the API key as the apikey query parameter on every request:
https://www.fanatical.com/feeds/minimal-feed-US.jsonl?apikey=YOUR_API_KEY
This documentation site is public and does not require an API key. The same key works across every feed your organisation is authorised for; if you need access extended to additional feeds, email the same address. Keep your API key out of client-side code and version control - treat it as a shared secret.
Acceptable use
The product data in these feeds - particularly pricing, discounts, and stock status - is commercially sensitive. Access is granted exclusively to partners enrolled in our affiliate programme under the terms of that agreement. The conditions below clarify what we expect from feed consumers and what will get an API key revoked.
You may
- Use the feed data to power product discovery, search, recommendations, comparison pages, and similar partner-facing experiences
- Display individual products, prices, and promotional information to your end users
- Cache the feed locally and serve from your cache between fetches - caching is encouraged
- Build derived products (rankings, filters, aggregated views) on top of the feed data
- Combine our data with data from other sources to enhance your own offerings
You may not
- Republish, redistribute, syndicate, or share the feed in whole or in substantial part - whether as raw files, mirrored downloads, or as a data product offered to third parties
- Share your API key with anyone outside your organisation, or with anyone who has not signed our affiliate agreement
- Expose the API key in client-side code, public repositories, or any context where it could be extracted by end users
- Use the data to build a competing storefront, price-comparison engine that does not link traffic to us, or scraping defense for a competitor
- Permit automated systems to consume the feed on behalf of unauthorised parties (for example, exposing it through a public API of your own)
About your API key
API keys are issued per organisation and identify your traffic. We monitor feed access; keys associated with usage patterns inconsistent with legitimate affiliate activity - bulk redistribution, sharing across organisations, no corresponding affiliate conversions - may be revoked without notice. Loss of API access does not affect your obligations under the affiliate agreement.
If your API key is exposed or you suspect unauthorised access, email affiliates@fanatical.com immediately and we will rotate it.
Reporting
If you become aware of feed data being republished publicly, please let us know - we treat this as a serious issue and act on tips.
Compression and caching
Feeds are served with content compression negotiated via the Accept-Encoding request header. gzip, br (Brotli), and zstd are all supported; most HTTP clients negotiate this transparently. Compressed responses are typically 80-90% smaller than the raw payload, especially for the JSONL feeds, so leaving compression enabled is strongly recommended.
Responses include standard cache headers - ETag, Last-Modified, Expires, and Age - so well-behaved clients can avoid re-downloading unchanged feeds. The recommended pattern is to store the ETag (or Last-Modified value) from each successful response and send it back as If-None-Match (or If-Modified-Since) on the next fetch; if the feed hasn't been regenerated since, you'll get a 304 Not Modified with no body and minimal bandwidth cost. Feed regeneration cadence varies by feed (see each feed's page); polling more frequently than the regeneration interval is wasteful but harmless thanks to the 304 responses.
Region & currency model
Every feed is published in two modes:
- Global: includes
included_regionsand aprice(and related) object whose keys cover every currency used by those regions. - Region-specific: keyed to a single ISO 3166-1 country code; price objects contain only that region's currency and
included_regionsis omitted.
Prices are in major units (19.99 is $19.99). Currency keys are ISO 4217 codes. Timestamps are Unix epoch seconds (NOT milliseconds, NOT ISO strings) - except for the AWIN and legacy feeds, which convert to ISO strings.
Conditional fields
Several fields appear only when the product has the relevant attribute:
| Field | Present when |
|---|---|
coupon |
The product has an active voucher |
promo_label |
The product is part of a featured promotion |
parent |
The product is a DLC, edition, or variant of a base product |
in_bundle |
The product is currently part of a bundle |
bundle_type, bundle_product_count, variable_price, bundle_tiers |
The product itself is a bundle |
bundle_price_messages |
Extended feed AND the product is a bundle |
included_regions |
Global feed (no country code specified) |
short_description_<lang> |
A translation exists for that language |
Bundle types
When bundle_type is present, the value tells you the pricing model:
| bundle_type | Meaning | Example bundle_price_messages.short |
|---|---|---|
standard |
Fixed price for the whole bundle | $19.99 for 10 games |
tiered |
Multiple tiers; bigger tier = more items | 5+ games from $4.99 |
pay-what-you-want |
Customer chooses any price above the minimum | $1 for 10 games |
build-your-own |
Customer picks N items from a pool | From $1.49 per game |
variable_price is true for everything except standard. Use it as a quick check when deciding whether to display a single price or a "from" price.
Related Links and info
- Awin Advertiser ID - 118821 - Fanatical Global
- Dynamic Ads Iframe Builder We offer a range of dynamic product ad units serving localised content to users. Insert your Awin publisher ID into the editor to build ad units with your tracking links.
- Dynamic Products API As an alternative to ad units we expose the underlying product data as a JSON API. This allows you to instantly find a set of products to present to a user (with localised pricing and availability). For most use cases, product feeds will be the most robust solution and give you the most flexibility, but you may have a use case for this API. This requires a different API key to the product feeds. Contact affiliates@fanatical.com to obtain one.