Esports Market Templates API: Richer Metadata Means Less Hard-Coding for Your Betting UI

Every new esports market a data provider ships tends to come with the same hidden cost for operators: someone on your engineering team has to hard-code its display name, its selection layout, and where it fits in your navigation. PandaScore's market templates endpoint now removes that cost entirely, with a manifest block that carries all of that information for every market template.

What's New

The GET /betting/market_templates endpoint now returns a manifest for every market template it serves, giving operators structured metadata for mapping and rendering any market directly from the API. The manifest includes:

• Display names with placeholder tokens filled in from the live feed
• Selection structure: positions, templates, labels, and home or away sides
• Parameters: which dynamic values exist and where to read them from the feed
• Shape: which UI components can render the market, such as over/under, handicap, or winner_2way
• Categorization: suggested navigation grouping across category, subcategory, and tags
• Features: BetBuilder availability per videogame and event type
• Live coverage: which videogames produce in-play odds for the template
• Availabilities: which videogames and event types support the template
• Subject: what the market is about, whether that's a match, game, player, team, or series

The API call itself hasn't changed. This is a drop-in enrichment to the existing endpoint.

Why This Matters for Operators

Most esports odds providers expect operators to maintain their own mapping layer: a table somewhere that says "this market ID renders as an over/under with these labels, in this category." That mapping has to be updated by hand every time a new market ships, and it's a common source of bugs when providers add markets faster than integration teams can keep up.

With manifests attached to every template, that mapping layer already exists inside the API response. Your front end can read the shape, selection structure and display name directly, without a developer needing to hard-code anything market by market.

What Happens When New Markets Launch

When PandaScore ships a new market template, such as the recent Call of Duty Total Kills Over/Under market, its manifest data is already present in the same response. That means new markets can be supported on your platform with no code changes required on your side. Rather than waiting on an integration ticket every time PandaScore's market catalogue grows, your UI can render new markets automatically as soon as they appear in the feed.

Who This Is For

This is most valuable for operators and platform teams building or maintaining their own betting UI on top of PandaScore's Odds API, particularly anyone currently maintaining a manual mapping table for market display and categorization. If that's you, this update should meaningfully cut the engineering overhead of keeping pace with new markets.

Want to see the manifest structure in detail, or talk through migrating your integration to use it? Get in touch with our team.