Terms of Service & Refund Policy

Plain language for indie builders, lawyer-readable when it matters.

Last updated: 2026-05-04. Operator: ParlayAPI. Contact: [email protected].

Contents

Summary Accounts and API keys Acceptable use Data, sources, redistribution Refund policy (the "fix-first" promise) Availability and SLA Liability and warranties Termination Changes to these terms Contact

Summary

You sign up, get an API key, query the endpoints, pay if you exceed the free tier. We try to keep the data accurate and the service up. If we ship a bug that breaks your workflow, we fix it fast or refund. We don't sell your queries, don't track your bets, and don't redistribute your data. You agree not to abuse the rate limits, scrape competitors through us, or break the law.

That's the gist. The rest of this page is the precise version.

Accounts and API keys

Acceptable use

You may:

You may not:

Data, sources, redistribution

ParlayAPI aggregates publicly-available sports odds from sportsbooks, prediction markets, and open-source community archives (nflverse, hoopR, CFBD, football-data.co.uk, SportsbookReviewsOnline, and others). We capture the data ourselves from each upstream's real endpoints; we don't synthesize, derive, or interpolate prices.

Open-source archives we re-distribute (nflverse, hoopR, CFBD, etc.) are licensed under MIT or comparable permissive terms. We comply with their license requirements and you, as our customer, are downstream of those licenses transitively.

You retain all rights to data you generate using the API (your model outputs, your analyses, your charts). We retain rights to the API itself, the schema design, and the aggregation/normalization logic.

Refund policy: the "fix-first" promise

Our philosophy: if you hit a real bug or a missing feature that's blocking you, our default is to fix it fast — not to refund and disappear. Refunds happen when we can't deliver.

The full policy:

  1. You file the issue. Email [email protected] describing what's broken or missing, with the endpoint, params, response you got, and what you expected. We open a support ticket on receipt.
  2. We commit to first response within 24 hours. US business hours; weekends slower. The response either ships a fix, schedules one, or explains why we can't.
  3. If it's a real bug we can fix in <1 hour of work, we fix it within 24 hours. Test, deploy, reply with the working endpoint URL. No refund needed because the service is now doing what you paid for.
  4. If we can't fix it in time, we refund. Pro-rated for the current billing period for monthly subs, full refund within 30 days of the original charge for first-month users. We won't argue about whether you got value from the rest of the month — if we promised something we couldn't deliver, that's on us.
  5. If you change your mind without a bug, we honor refunds within 7 days of charge for any reason. After day 7, we credit unused time toward future months.
  6. Refunds for downtime: if our published SLA (99.9%) is missed in a calendar month, you get a 10% credit on the next invoice automatically. Sustained downtime above 4 hours triggers a manual refund request review.

Excluded from refund:

Availability and SLA

Liability and warranties

The service is provided as-is. We make our best effort to keep data accurate and the API available, but we don't warrant any of:

To the maximum extent permitted by law, our total liability to you for any claim arising from the service is capped at the amount you paid us in the 12 months prior to the claim.

Termination

You can cancel any time at /dashboard. We don't demand a reason. We'll process the cancellation effective at the end of your current billing period (so you get the rest of the month you paid for).

We can terminate accounts that violate the acceptable-use rules. We'll email you first unless we believe the activity is malicious or fraudulent, in which case we'll lock the keys immediately and explain after.

Changes to these terms

We update this page as the service evolves. Material changes (new restrictions, refund-policy reductions, fee increases) will be emailed to active subscribers 30 days before they take effect. Day-one customers always get grandfathered on the policy that was in effect when they signed up, until and unless we email them with explicit notice of a change to their plan.

Contact