Acceptable Use Policy
What you can do with the API, what you can't, and what happens when you cross the line.
1. What you can do
- Build betting tools. +EV scanners, arb finders, line-shop bots, Discord notifiers, dashboards, models. That's the whole point of the API.
- Resell aggregated insights. If you're charging customers for an EV/arb/notification product built on our data, you're fine. We are part of your stack.
- Cache results. Hold our responses for as long as your application needs. We don't impose a TTL on derived data.
- Run on any cloud, on-prem, or local. No geo-restriction beyond what your bookmakers themselves impose.
- Use our data in published content (blog posts, newsletters, social media) with attribution to ParlayAPI as the data source.
2. What you can't do
- Resell our raw odds feed verbatim as a data product without permission. Building EV/arb/model output on top of our data and selling that is fine; mirroring our API and reselling it as a competing odds API is not. If you're not sure where the line is, email us.
- Share a single API key across multiple companies or unrelated users. One key, one customer. Use one of the higher tiers if you need multiple keys for sub-accounts (Business+).
- Circumvent credit limits by signing up multiple free-tier accounts to stitch together a paid tier's volume. We rate-limit by IP and by email-canonical form to catch this; accounts caught will be merged or terminated.
- Use the data to facilitate bet manipulation, match-fixing, or unauthorized line setting. If we receive a credible report we cooperate with regulators.
- Disrupt the service via deliberate overload, denial of service, or by exploiting bugs to degrade other customers' experience. We monitor and block.
- Republish other customers' data. If you're a tier with access to aggregated stats (book coverage, source health, etc.), those views are for your use, not republication.
3. Gambling jurisdiction
We do not place bets, do not facilitate placing bets, and do not provide a gambling service. We are a data API. Whether you may legally use our data depends on where you are and how you use it. Some states and countries restrict the construction or distribution of betting-related software. That's on you to research; we do not block by IP.
4. Bookmaker terms of service
Many bookmakers explicitly prohibit automated or programmatic access to their odds. We source our data from public endpoints (book websites, public APIs, exchange feeds), and we do not authorize you to bypass any bookmaker's own ToS. Using our API does not grant you any rights against the bookmakers themselves; if FanDuel decides to ban your sportsbook account because you appear to be running an arb bot, that's between you and FanDuel.
5. Reporting bugs and security issues
- Bugs in our API (wrong data, slow endpoints, broken auth): email [email protected] or open a thread in our community Discord.
- Security vulnerabilities (auth bypass, data leak, injection, anything sensitive): email [email protected]. Do not post publicly until we've had a chance to fix. We do not run a paid bug bounty but we credit researchers publicly with permission and we'll engage in good faith.
6. Enforcement
If we believe an account is violating this policy:
- First contact: an email or dashboard banner asking you to stop.
- Repeat: a temporary suspension while we discuss.
- Egregious or unresponsive: termination, with a refund of the unused prorated portion of any paid period.
We don't enjoy this. We will always try to talk first. Termination for cause does not remove your right to request data deletion under our privacy policy.
7. Changes
If we materially change this policy we email every active account. Last revision date is below.