NCAAF Odds API

Our NCAAF odds API delivers NCAAF odds, player props, status and results for every game from 43 bookmakers, 38 of them Australian. leagueID=NCAAF. Free tier available.

Whether you're building a betting app, an odds comparison tool or a pricing model, the NCAAF odds API gives you structured data in the SportsGameOdds v2 shape so you can move fast.

Covering more than NCAAF? The American Football returns CFL, NFL and NCAAF from a single sport-level request.

NCAAF Odds API Features

Every endpoint is filterable, so you pull exactly the markets you need. Coverage spans 129 teams and 71 events currently carried, with 10 market families.

Available NCAAF betting markets include:

• Head to head / moneylines (2-way and 3-way markets)
• Lines, spreads and handicaps
• Totals (over/under)
• Alternative lines
• Player props and game props
• Period-specific markets (1h, 1q)

All market data is pre-match, refreshed every ~2 minutes; see pricing for what each plan can see.

NCAAF Player Props API

Access 3 NCAAF player proposition markets through the same endpoint — Touchdowns, Receptions — for every player the books price. See the player prop odds API for the market list across every sport.

Filter by playerID, stat type or bookmaker to return only the props you need.

NCAAF Odds API with Results

SockOdds delivers NCAAF odds and event data together in one response — no need to stitch data from multiple sources. Each response includes:

• Upcoming NCAAF events with status flags
• Home and away team data with ids
• Players with production ids where present
• Full odds coverage: lines, totals, head to head, props and alternative lines
• Results and scoringSupported flags where the source grades

Line movement tracking is yours to build: every bookmaker entry carries lastUpdatedAt, and finished events are retained.

Quick start: your first NCAAF odds API call

Getting NCAAF odds takes a single HTTP request:

https://api.sockodds.com/v2/events?apiKey=YOUR_API_KEY&oddsAvailable=true&leagueID=NCAAF&limit=10

curl -X GET "https://api.sockodds.com/v2/events?oddsAvailable=true&leagueID=NCAAF&limit=10" -H "x-api-key: YOUR_API_KEY"

const response = await fetch("https://api.sockodds.com/v2/events?oddsAvailable=true&leagueID=NCAAF&limit=10", { headers: { "x-api-key": "YOUR_API_KEY" } });
const { data, nextCursor, notice } = await response.json();
console.log(JSON.stringify(data, null, 2));

import requests

response = requests.get("https://api.sockodds.com/v2/events", params=dict(oddsAvailable="true", leagueID="NCAAF", limit="10"), headers={"x-api-key": "YOUR_API_KEY"})
output = response.json()
print(output["data"])

require 'net/http'
require 'json'

uri = URI("https://api.sockodds.com/v2/events?oddsAvailable=true&leagueID=NCAAF&limit=10")
req = Net::HTTP::Get.new(uri)
req['x-api-key'] = 'YOUR_API_KEY'
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |http| http.request(req) }
puts JSON.pretty_generate(JSON.parse(res.body)['data'])

<?php
$ch = curl_init("https://api.sockodds.com/v2/events?oddsAvailable=true&leagueID=NCAAF&limit=10");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_HTTPHEADER, ['x-api-key: YOUR_API_KEY']);
$output = json_decode(curl_exec($ch), true);
curl_close($ch);
print_r($output['data']);

import java.net.URI;
import java.net.http.*;

HttpClient client = HttpClient.newHttpClient();
HttpRequest request = HttpRequest.newBuilder()
    .uri(URI.create("https://api.sockodds.com/v2/events?oddsAvailable=true&leagueID=NCAAF&limit=10"))
    .header("x-api-key", "YOUR_API_KEY").GET().build();
HttpResponse<String> response = client.send(request, HttpResponse.BodyHandlers.ofString());
System.out.println(response.body());

req, _ := http.NewRequest("GET", "https://api.sockodds.com/v2/events?oddsAvailable=true&leagueID=NCAAF&limit=10", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, err := http.DefaultClient.Do(req)
if err != nil { log.Fatal(err) }
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

This returns all available markets — lines, totals, head to head and props — for upcoming NCAAF events.

To narrow to a specific market, use the oddID parameter, with PLAYER_ID standing for every player:

https://api.sockodds.com/v2/events?apiKey=YOUR_API_KEY&oddsAvailable=true&leagueID=NCAAF&oddID=touchdowns-PLAYER_ID-game-yn-yes&includeOpposingOdds=true

curl -X GET "https://api.sockodds.com/v2/events?oddsAvailable=true&leagueID=NCAAF&oddID=touchdowns-PLAYER_ID-game-yn-yes&includeOpposingOdds=true" -H "x-api-key: YOUR_API_KEY"

const response = await fetch("https://api.sockodds.com/v2/events?oddsAvailable=true&leagueID=NCAAF&oddID=touchdowns-PLAYER_ID-game-yn-yes&includeOpposingOdds=true", { headers: { "x-api-key": "YOUR_API_KEY" } });
const { data, nextCursor, notice } = await response.json();
console.log(JSON.stringify(data, null, 2));

import requests

response = requests.get("https://api.sockodds.com/v2/events", params=dict(oddsAvailable="true", leagueID="NCAAF", oddID="touchdowns-PLAYER_ID-game-yn-yes", includeOpposingOdds="true"), headers={"x-api-key": "YOUR_API_KEY"})
output = response.json()
print(output["data"])

require 'net/http'
require 'json'

uri = URI("https://api.sockodds.com/v2/events?oddsAvailable=true&leagueID=NCAAF&oddID=touchdowns-PLAYER_ID-game-yn-yes&includeOpposingOdds=true")
req = Net::HTTP::Get.new(uri)
req['x-api-key'] = 'YOUR_API_KEY'
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |http| http.request(req) }
puts JSON.pretty_generate(JSON.parse(res.body)['data'])

<?php
$ch = curl_init("https://api.sockodds.com/v2/events?oddsAvailable=true&leagueID=NCAAF&oddID=touchdowns-PLAYER_ID-game-yn-yes&includeOpposingOdds=true");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_HTTPHEADER, ['x-api-key: YOUR_API_KEY']);
$output = json_decode(curl_exec($ch), true);
curl_close($ch);
print_r($output['data']);

import java.net.URI;
import java.net.http.*;

HttpClient client = HttpClient.newHttpClient();
HttpRequest request = HttpRequest.newBuilder()
    .uri(URI.create("https://api.sockodds.com/v2/events?oddsAvailable=true&leagueID=NCAAF&oddID=touchdowns-PLAYER_ID-game-yn-yes&includeOpposingOdds=true"))
    .header("x-api-key", "YOUR_API_KEY").GET().build();
HttpResponse<String> response = client.send(request, HttpResponse.BodyHandlers.ofString());
System.out.println(response.body());

req, _ := http.NewRequest("GET", "https://api.sockodds.com/v2/events?oddsAvailable=true&leagueID=NCAAF&oddID=touchdowns-PLAYER_ID-game-yn-yes&includeOpposingOdds=true", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, err := http.DefaultClient.Do(req)
if err != nil { log.Fatal(err) }
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

OddIDs follow the format {statID}-{statEntityID}-{periodID}-{betTypeID}-{sideID}, where the entity is a player for props and home, away or all for team and game markets.

Tips to keep responses fast:

• Add bookmakerID=bearbet,betfocus to limit to the bookmakers you care about
• Use includeOpposingOdds=true so you only need to specify one side of a market
• Keep your oddID list tight — only request markets you're actively using

What a NCAAF response looks like

Every event returns an odds object keyed by oddID. Here's a real market from the feed with the bookmaker list cut to two books:

{
  "eventID": "ncaaf_2026-09-25_california_vs_clemson",
  "leagueID": "NCAAF",
  "odds": {
    "points-all-game-ou-over": {
      "oddID": "points-all-game-ou-over",
      "opposingOddID": "points-all-game-ou-under",
      "marketName": "Total Points",
      "statID": "points",
      "statEntityID": "all",
      "periodID": "game",
      "betTypeID": "ou",
      "sideID": "over",
      "fairOdds": null,
      "bookOdds": null,
      "byBookmaker": {
        "123bet": {
          "odds": "-127",
          "decimal": 1.787,
          "available": true
        },
        "bearbet": {
          "odds": "-110",
          "decimal": 1.909,
          "available": true
        }
      }
    }
  }
}

Two things worth noting. Odds values are strings, not numbers, so -108 arrives as "-108" — that keeps the leading + intact on underdog prices — and every book also carries decimal, because Australian books quote decimal. bookOdds is the consensus with the vig left in; fairOdds is the de-vigged price on Rookie and above, null where it cannot be computed.

NCAAF Odds API Technical Specifications

API Architecture

• REST API — Simple HTTP endpoints with JSON responses, identical to the SportsGameOdds v2 paths
• Native WebSocket snapshots - Pro/Platform at /v2/stream/events; polling-backed, with unchanged upstream freshness
• Rate limits — per-key, per-minute meters that bind under concurrency; plans sized to your usage
• Authentication — secure API key access via the x-api-key header or apiKey query parameter

Data Update Speed

• Odds updates — every ~2 minutes across every bookmaker lane
• Event status — status flags and info.stale tell you exactly how current a price is

Developer Resources

• Interactive documentation — live examples, copy-paste snippets and an AI (vibe coding) context
• SDKs & libraries — the SportsGameOdds SDKs for TypeScript, Python, Ruby, Go and Java work unchanged with the base URL pointed here
• Postman collection — pre-built requests ready to run
• Support — email support on every plan, priority on paid plans

NCAAF betting market coverage in the SockOdds API, by category

See every NCAAF market with its exact oddID in the markets browser.

Use Cases

• Arbitrage & +EV tools — compare NCAAF odds across every Australian bookmaker to uncover arbitrage opportunities and positive expected value angles.
• Odds comparison platforms — display NCAAF odds from every book side by side for comprehensive line shopping.
• Pricing models & trading — use NCAAF market data as inputs for proprietary pricing algorithms and betting strategies.
• Sports analytics & research — examine NCAAF line movements and betting-market patterns, and build predictive models on retained events.
• Betting automation — build systems that monitor NCAAF lines across bookmakers and trigger actions when your target odds appear.
• Sportsbook & fantasy apps — power your NCAAF product with reliable odds, status and bet-slip deeplinks.

NCAAF Odds API Documentation

Our interactive documentation covers everything you need to integrate NCAAF odds into your project:

• Full endpoint reference with parameters and response schemas
• Live request and response examples
• Code snippets in Python, JavaScript, Ruby, Go and Java
• Authentication setup and API key management
• Rate limiting and the notice field
• Error handling and troubleshooting

View documentation

For more on querying /v2/events with NCAAF-specific examples, see the API documentation.

Frequently asked questions