Skip to content

Plans / no overages

Choose your feed speed.

Start with every route for 14 days—no credit card. Keep the complete historical and current REST surface on Basic, or add higher limits and ordered live delivery on Pro. Annual plans include two months free.

Full field test

Trial

Pro-level access for a real integration, not a restricted demo.

Free

14 days · no card

  • 10,000 REST calls
  • 120 calls per minute
  • 365-day history
  • 1 WebSocket connection
  • 20,000 live messages
  • Scores, stats, plays and verified odds
Start the trial

REST foundation

Basic

For research, prototypes and products that can poll and cache.

$5 / month

$50 yearly

  • 25,000 REST calls / month
  • 60 calls per minute
  • 90-day history
  • All catalogue and game routes
  • Play-by-play and statistical routes
  • Server-side commercial display
Try Basic

Live operations

Pro

For alerts, live centres and market-aware products.

$10 / month

$100 yearly

  • 100,000 REST calls / month
  • 120 calls per minute
  • 365-day history
  • Up to 3 WebSocket connections
  • 100,000 live messages / month
  • Verified fixture odds and price history
Try Pro

Selection guide

REST snapshot or live delta?

Choose Basic when your application loads schedules, standings, results, stats or periodic score snapshots. Poll active fixtures from your backend, respect response freshness, and let your own cache serve the audience.

Choose Pro when seconds matter. Load initial state from REST, then use WebSockets for ordered score and market deltas. Pro is designed for live centres, newsroom tools, alerts, second-screen experiences and quantitative monitoring.

FAQ

Before the faceoff.

What data is included in the trial?

The 14-day trial includes the full REST catalogue, live fixtures, play-by-play, statistics, standings, transactions, verified market data and one WebSocket connection. No card is required.

Which plan is right for a live scoreboard?

Basic works for server-side polling at sensible intervals. Choose Pro when score and market changes need to arrive automatically over WebSockets.

Do end-user page views count as requests?

Only calls your server makes to Lacrosse API count. Cache responses in your own application so one API request can support many page views and your key stays private.

Will traffic spikes create surprise charges?

No. Plans have hard limits. Once a limit is reached, additional calls return an error rather than creating overage fees.

Does every WebSocket update count as a REST call?

No. Stream messages use a separate outbound-message allowance. REST calls are counted only when your application requests a REST endpoint.

Are market prices an official settlement source?

No. Odds and market prices are informational and analytical context. They are provider observations, not an official settlement source.