MMA Odds API: How to Pull Fight Cards, Moneylines & Props Without Scraping Books

A practical MMA odds API guide for fight-card boards, moneylines, totals, method/round props, bookmaker filters, and research UIs. Endpoints, refresh strategy, Next.js patterns, and when to use Cito for UFC markets.

Author:
Cito Team

Direct Answer: What Is an MMA Odds API?

An MMA odds API returns structured betting markets for mixed martial arts fights — moneylines, totals, method-of-victory and round props, bookmaker labels, and timestamps — as JSON you can render in odds boards, matchup widgets, Discord bots, and research tools.

Most commercial demand for “MMA odds API” is UFC-first: numbered events, Fight Nights, full undercards, and bookmaker-specific lines. Cito’s stack under /api/v1/ufc/... is built for that product shape — event-wide markets plus per-bout deep links — without scraping sportsbook HTML.

JobEndpoint familyBest for
Full card oddsGET /ufc/events/{eventIdOrSlug}/oddsEvery fight on a card, one request
Fight-card aliasGET /ufc/fight-cards/{eventIdOrSlug}/oddsSame data, alternate path family
One fightGET /ufc/fights/{boutId}/oddsMatchup pages and widgets
Bout aliasGET /ufc/bouts/{boutId}/oddsSame fight via bout ID

Docs: UFC API reference. Free key: signup. Pair performance context with the UFC Stats API guide or the UFC Odds API deep dive.

Why People Search “MMA Odds API” (Not Just “UFC Odds”)

Search intent is usually product work, not trivia:

  • Fight-night preview boards — every bout on the card with ML + props

  • Book comparison tables — same fight across DraftKings, FanDuel, etc.
  • Bots & agents — “What’s the main-event moneyline?”
  • Model features — prices as inputs (not sportsbook placement)
  • Research UIs — join odds + fighter stats + rankings on one page

    • “MMA” is the category. UFC is where most public card volume, bookmaker coverage, and stable fight IDs live for API products. If your app is UFC-centric, optimize for event and bout IDs — not free-text fighter names alone.

    What Good MMA Odds JSON Looks Like

    A production-ready payload is more than a string of American odds. You want:

    • Stable bout IDs joined to red/blue (or fighter A/B) identities
    • Market type (moneyline, total, method, round, etc.)
    • Outcome rows (label + price) suitable for tables
    • Bookmaker identity on every price
    • Timestamps / data-quality metadata so UIs can say “stale” instead of lying

    Never render orphan prices. Always join odds rows to the event card (/ufc/events/{id}/bouts) so fighter names, weight class, and order of fight stay correct when lines move.

    Cito MMA (UFC) Odds Endpoints

    Base: https://api.citoapi.com/api/v1

    Auth: x-api-key: YOUR_API_KEY

    bash
    # Discover the cardGET /ufc/events/upcomingGET /ufc/events/{eventIdOrSlug}GET /ufc/events/{eventIdOrSlug}/bouts # All markets on one cardGET /ufc/events/{eventIdOrSlug}/odds?bookmaker=allGET /ufc/fight-cards/{eventIdOrSlug}/odds?bookmaker=draftkings # One fightGET /ufc/fights/{boutId}/odds?bookmaker=draftkingsGET /ufc/bouts/{boutId}/odds?bookmaker=all

    Example: full card, all books

    bash
    curl "https://api.citoapi.com/api/v1/ufc/events/{eventIdOrSlug}/odds?bookmaker=all" \  -H "x-api-key: YOUR_API_KEY"

    Example: one fight, one book

    bash
    curl "https://api.citoapi.com/api/v1/ufc/fights/{boutId}/odds?bookmaker=draftkings" \  -H "x-api-key: YOUR_API_KEY"

    Bookmaker filter

    QueryBehavior
    bookmaker=allEvery available sportsbook in the response
    bookmaker=draftkingsNarrow to that book
    bookmaker=fanduel / betonlineSame idea for other supported books

    Exact book coverage can vary by card and market type — design UIs to handle empty markets gracefully.

    When a user (or AI agent) says “build an MMA odds page”:

  • GET /ufc/events/upcoming — pick a card

  • GET /ufc/events/{eventIdOrSlug} — title, date, venue context
  • GET /ufc/events/{eventIdOrSlug}/bouts — fight list + bout IDs
  • GET /ufc/events/{eventIdOrSlug}/odds?bookmaker=all — board data
  • Optional: GET /ufc/fights/{boutId}/odds?bookmaker=draftkings for a deep link
  • Optional stats: GET /ufc/fighters/{slug}/stats — stats guide
  • Optional ranks: GET /ufc/rankings/meta/{division} — rankings guide

    • That pipeline powers previews, Discord /odds, and research tools without a sportsbook scraper farm.

    Next.js: Server-Side Event Odds Loader

    TypeScript
    const API = "https://api.citoapi.com/api/v1"; export async function getMmaEventOdds(  eventIdOrSlug: string,  apiKey: string,  bookmaker: string = "all",) {  const url = new URL(    `${API}/ufc/events/${encodeURIComponent(eventIdOrSlug)}/odds`,  );  url.searchParams.set("bookmaker", bookmaker);   const res = await fetch(url, {    headers: { "x-api-key": apiKey },    // Fight week: short revalidate. Off-week marketing pages can go longer.    next: { revalidate: 120 },  });   if (!res.ok) throw new Error(`mma odds failed: ${res.status}`);  return res.json();}

    Keep keys server-side. Client components should call your own BFF/route handler, not ship the API key to the browser.

    Refresh Strategy (What Actually Matters)

    Product typeSuggested refresh
    Marketing sample boardHourly or on-demand ISR
    Fight-week odds board1–5 minutes
    Discord /oddsCache 1–3 minutes per bout/event
    Model feature snapshotStore price + timestamp; snapshot at lock or query time
    Live round clocksUse live UFC endpoints — do not poll odds every second

    Odds are market prices, not strike clocks. Over-polling burns quota and does not make a better product past a sensible cadence.

    Odds vs Stats vs Live vs Rankings

    QuestionUse
    “What’s the moneyline / prop?”Odds routes
    “Who lands more significant strikes?”Stats routes
    “What round is it / what’s the clock?”Live routes
    “Where are they ranked?”Rankings routes

    Serious MMA apps join these layers. Cito keeps them on explicit endpoint families so agents and UIs do not mix prices with combat rows.

    Build Targets an MMA Odds API Unlocks

    • Full-card odds boards for upcoming UFC events

    • Single-fight moneyline and prop widgets
    • Multi-book comparison tables
    • Research dashboards (odds + stats + rankings)
    • Discord / Telegram bots
    • AI agents answering main-event and prop questions
    • Feature stores for forecasting models (with your own labels)

    Common Mistakes

  • Scraping sportsbook HTML — anti-bot walls, silent breakage, ToS risk.
  • Prices without bookmaker labels — always show which book a line came from.
  • No timestamps — lines move; show last-updated context.
  • Polling every second — wasteful; use revalidation windows.
  • Hardcoding fighter names only — join via boutId and card order.
  • Treating odds as live fight stats — different surfaces entirely.
  • Assuming every prop exists on every book — handle partial coverage.

    • Compliance Note (Read This)

    An MMA odds API is for data display and research in products you build. You are responsible for:

    • Legal and compliance requirements in your jurisdiction
    • Not implying you are a licensed sportsbook unless you are
    • Clear UI labeling of bookmakers and timestamps
    • Following Cito’s terms for redistribution and commercial use

    Cito provides structured odds data. Your product’s legal packaging is on you.

    FAQ: MMA Odds API

    Is there an MMA odds API for developers?

    Yes. For UFC-centric MMA products, Cito exposes event and fight odds under /api/v1/ufc/events/{id}/odds, fight-card aliases, and per-fight /ufc/fights/{boutId}/odds routes.

    Can I filter by sportsbook?

    Yes. Use bookmaker=all or a specific book (for example draftkings, fanduel, betonline) depending on coverage for that card.

    Does it include props?

    Where books offer them for a card, Cito’s odds surfaces include markets beyond simple moneylines — totals, method of victory, and round-oriented props when available.

    How do I get bout IDs?

    Load GET /ufc/events/{eventIdOrSlug}/bouts, then call fight-level odds for the bouts you want to feature.

    MMA odds vs UFC odds — what’s the difference?

    “MMA odds API” is the category search. “UFC odds API” is the concrete product surface most developers ship against. See also the UFC Odds API guide.

    Can AI coding agents integrate this quickly?

    Yes. Point agents at https://citoapi.com/llms.txt and https://citoapi.com/ai/endpoints, resolve an upcoming event, then call event/fight odds with a server-side key from signup.

    Next Steps

  • Create a free Cito key

  • GET /ufc/events/upcoming and open one event
  • Fetch /ufc/events/{id}/odds?bookmaker=all
  • Deep-link the main event with /ufc/fights/{boutId}/odds
  • Add fighter context from the UFC Stats API
  • Read full UFC docs

    • Read more from us

    Start building with esports data today

    Free tier available. Same API shape across Call of Duty, Fortnite, LoL, Dota 2, and more.

    Create free account