Acceptable Use Policy

ParlayAPI

Effective Date: May 7, 2026

Last Updated: October 14, 2026

1. Purpose and Scope

This Acceptable Use Policy ("AUP") governs all use of the ParlayAPI service, including the API endpoints served from parlay-api.com, our documentation, dashboards, customer keys, and any associated SDKs or sample code (collectively, the "Service"). By generating an API key, integrating the Service, or otherwise accessing parlay-api.com, you ("Customer," "you") agree to comply with this AUP. This AUP supplements, and does not replace, our Terms of Service and Privacy Policy.

ParlayAPI distributes sports betting odds, line movement, and play-by-play data that we collect from publicly observable sources, together with values we calculate from that data (for example, no-vig prices, expected value, and arbitrage figures). Our sources include sportsbooks licensed in one or more US states, sportsbooks that are not licensed in any US state, daily fantasy apps, betting exchanges, and prediction markets. Our sources do not endorse or sponsor the Service, and we do not represent that any source is licensed, or that any use of its data is lawful, in your jurisdiction. The data we serve is operationally sensitive and time-decaying. Misuse imposes direct costs on us, on our upstream sources, and on other customers who depend on stable rate-limit budgets. The rules below exist for that reason.

2. Prohibited Content and Geographies

You may not use the Service, or allow any downstream user of your application to use the Service, to:

• Provide gambling-related assistance, recommendations, picks, or wagering tools to any person you know or should reasonably know to be under the age of 21 (or under the local minimum gambling age, whichever is higher).
• Facilitate, enable, or promote unlicensed sportsbook activity, illegal bookmaking, or wagering in any US state or foreign jurisdiction where sports betting is not legally permitted, including but not limited to states with active prohibitions on online sports wagering.
• Distribute the Service or its outputs into jurisdictions subject to US sanctions (including OFAC-restricted countries) or to any individual or entity on the Specially Designated Nationals list.
• Promote match-fixing, insider information trading, or any conduct that would violate sports integrity rules of the leagues whose data passes through the Service.
• Knowingly serve users who have been self-excluded from gambling activity in a state with a registered self-exclusion program, where such information is reasonably available to your application.

You are responsible for performing geo-verification, age-verification, and self-exclusion checks at your application layer. The Service is not a compliance service.

3. Prohibited Technical Actions

You may not, and may not permit any third party to:

• Circumvent, disable, or attempt to evade any rate limit, quota, throttling rule, IP allowlist, or fingerprinting control we apply to your account or to the Service generally. Rotating through multiple keys, residential proxies, distributed runners, or shell accounts to exceed your contracted quota is a material breach.
• Share, lease, transfer, sub-license, or resell your API key. Each key is bound to a single legal entity and a single application. If you operate multiple products, each requires its own key under your account.
• Reverse-engineer, probe, or systematically map our rate-limit logic, authentication flow, internal endpoint structure, or upstream source identity for the purpose of bypassing controls, replicating our infrastructure, or building a competing aggregator.
• Conduct automated extraction, harvesting, or wholesale copying of our data sources, including but not limited to parlay-api.com/docs, internal admin surfaces, our blog content, our cached data files, or any non-API surface we operate. The Service is the only authorized means of bulk data access, and only within your contracted quota.
• Obscure or misrepresent your identity, including by spoofing User-Agent headers to imitate browsers, stripping required client identification headers we mandate in documentation, hiding your originating IP behind an anonymizing network for the purpose of evading enforcement, or registering accounts under false business identities.
• Probe for security vulnerabilities outside the scope of our published security disclosure program, attempt unauthorized access to other customers' data, or deliberately submit malformed requests intended to cause service degradation.
• Cache or persist responses in violation of the cache-control directives we serve, particularly for time-sensitive in-play markets where stale data poses harm to downstream users.

4. Prohibited Business Uses

No self-serve tier automatically grants the following rights. Each requires a separate written agreement signed by ParlayAPI that expressly permits the specific use. The Terms of Service, including Section 4.4 on existing agreements and notice, govern the license and transition:

• Redistributing Output, whether raw, reformatted, combined, white-labeled, or relabeled, as a feed, API, dataset, file, or download.
• Offering public or customer-facing displays, alerts, applications, analytics, or other commercial derived products based on Output. Internal processing does not by itself grant downstream distribution or commercial product rights.
• Selling, licensing, or providing access to historical archives derived from our Service to third parties without a separate written redistribution agreement.
• Using the Service as an upstream for a competing odds API or sports data service. Buying an Enterprise or Scale subscription or disclosing the dependency is not permission.
• Combining our outputs with another aggregator's outputs and offering the union as a single feed without our written consent.

5. Per-Tier Rules

Tier-specific obligations apply in addition to the rules above:

Free Tier: Personal evaluation and non-commercial research use only, subject to the current credit allowance, endpoint costs, and access windows at pricing. The allowance is measured in credits, not an equivalent number of requests. You may not deploy a Free-tier key into a revenue-generating product, monetized website, paid mobile application, or any service where the API output is gated behind payment, advertising, or subscription. Non-commercial educational and academic use is permitted.

Paid Self-Serve Tiers, including Starter, Pro, Business, Enterprise, and Scale: Limited internal research and business analysis within a single customer legal entity, subject to the Terms and contracted credit and access limits. Customer-facing use, commercial derived products, public display, resale, redistribution, sublicensing, and white-label rights are not included merely because the tier is paid. Single application per key; no key sharing.

Separately Negotiated Agreements: Any additional rights must be expressly granted in a written agreement signed by ParlayAPI and are limited to its named customer, use, data scope, audience, delivery method, and duration. No tier includes an SLA or additional licensing rights merely by its name. Existing signed grants and the notice requirements in Terms Section 4.4 remain in effect.

6. Enforcement and Penalties

We escalate enforcement proportionate to the violation. Typical sequence:

1. Warning. First-instance, low-severity violations result in a written warning to the account email on file, with a remediation deadline (typically 7 days for technical violations, 14 days for business-use violations).
2. Key Revocation. Continued violation, or any first-instance high-severity violation (e.g., key sharing, rate-limit evasion, redistribution), results in immediate revocation of the offending API key. A replacement key may be issued at our discretion after remediation.
3. Account Termination. Repeat violation, refusal to remediate, or any first-instance critical violation (e.g., serving minors, sanctioned-geography distribution, data exfiltration) results in termination of all keys and the customer account. Pre-paid amounts are non-refundable in termination-for-cause scenarios.
4. IP and ASN Blocking. Where account termination is followed by attempts to re-register or to access the Service from related infrastructure, we will block the originating IP ranges and ASNs at our edge.
5. Civil Action. For violations involving willful infringement, contractual breach causing measurable damages, or interference with our access to upstream sources, we reserve all rights to pursue civil remedies including injunctive relief, damages, and attorneys' fees.

We may also suspend Service immediately, without prior notice, where continued operation poses an active risk to the Service, to other customers, or to our access to upstream sources.

7. Reporting Violations

Suspected violations of this AUP, security vulnerabilities, or abusive use of the Service should be reported to [email protected]. Reports may be submitted anonymously. We treat all good-faith reports confidentially and do not retaliate against reporters who follow our published disclosure process.

For urgent matters involving active abuse, include "URGENT" in the subject line. Routine policy questions should be sent to [email protected].