Basic
For small apps, research tools and scoreboards that check for updates at sensible intervals.
$5/month
$50/year
- • 25,000 REST requests/month
- • 60 requests/minute
- • 90-day history
- • Show scores in your own website or app
- • REST API access
Try every main feature for 14 days with no card required. After the trial, choose Basic for straightforward REST access or Pro for live WebSocket updates. All prices are listed in US dollars. Applicable taxes may be added depending on your location. Annual plans give you two months free.
For small apps, research tools and scoreboards that check for updates at sensible intervals.
$5/month
$50/year
For live dashboards, alerts and trading tools that need updates as they happen.
$10/month
$100/year
For larger products, data redistribution or custom commercial terms.
Contact us
Negotiated
Choose Basic when your application can request scores on demand or check an active tie every 10–15 seconds. Its 25,000 monthly requests are designed to cover roughly one 30-tie event with room for match lists, metadata and normal retries. It is a good fit for hobby projects, research, small scoreboards and early product ideas.
Choose Pro when your application needs score changes to arrive automatically. The WebSocket feed is the better choice for trading dashboards, alerts and live user experiences because it avoids constant polling. Pro also includes 100,000 REST requests for initial loads, history, development and recovery.
Contact us about Enterprise when you need to redistribute the raw feed, serve data to third parties, use substantially larger limits, retain more history or agree custom support and licensing terms.
Yes. Basic is $5 monthly or $50 yearly. Pro is $10 monthly or $100 yearly.
No. There is one 14-day Pro trial for each verified account. After the trial, choose a paid plan to keep access.
No. Basic and Pro have hard usage limits. When a limit is reached, requests return an error instead of creating overage charges.
An MLP-style event contains about 30 team ties. Polling the active tie every 10–15 seconds uses roughly 10,000–16,000 state requests across the event, leaving room for match lists, details and retries. Your exact use will depend on tie duration and how many endpoints you request.
They should not. Call Pickleball Live API from your server, cache the response and serve your own users from that cache. This protects your key and lets one upstream request support many page views.
No. WebSocket messages use the separate live-message allowance. REST requests count only when your application calls a REST endpoint.
Yes. Manage upgrades, payment methods and cancellation through the customer portal.
All new accounts begin with the same 14-day Pro trial. You can cancel through the customer portal at any time. Basic and Pro use hard limits, which means the service stops additional usage rather than adding an unexpected bill. Scores are supplied for display and analysis and are not an official settlement source.