Skip to content
All legal documents

API Terms

Developer Portal and SplitWinner API terms — IP, restrictions, sandbox disclosure, accuracy disclaimer, liability cap.

Version 2 · Effective June 13, 2026

SplitWinner API Terms

Last updated: June 2026 — version 2

These terms govern your use of the SplitWinner API ("API") and the developer portal at splitwinner.com/developers. They are a binding contract between you (and the entity you represent) and SplitWinner ("we", "us"). By creating an account, generating an API key, or sending a request to the API, you agree to these terms. If you do not agree, do not use the API.

Paid tiers (starter, pro, enterprise) require a separate, signed Master Services Agreement before access is granted. Where the MSA conflicts with these terms, the MSA controls for that customer.

1. The Sandbox is Synthetic — Fully Disclosed

The free sandbox tier returns mocked data. The sandbox does not query our database, does not return real predictions, does not reflect real historical results, and does not pass through any real upstream market feed. Responses are generated locally on each request.

What is faithful to production:

  • Response shape — JSON keys, types, nesting, and required vs optional fields match the paid API one-for-one.
  • HTTP semantics — status codes, content types, problem+json error envelopes, cache headers, and rate-limit headers behave as they would in production.
  • Format of values — identifiers, timestamps, sport names, team strings, odds shapes, and confidence ranges are in the same format and within the same plausible ranges as production data.

What is not faithful and must not be relied on:

  • The values themselves are synthetic. Identifiers, timestamps, scores, odds, confidence numbers, audit hashes, and aggregates are generated for integration testing only. They are not predictions.
  • Edge-case behavior (rate limits under load, slate-day boundary edges, upstream-error pass-throughs, conformal-coverage tails) may differ from production. The documented integration coverage is approximately 90%; the paid contract is the exact contract.

You acknowledge and agree that sandbox responses must not be presented to any third party as actual SplitWinner predictions, must not be redistributed or sold, and must not be used to make real betting, investment, or operational decisions.

2. License Grant

We grant you a limited, non-exclusive, non-transferable, non-sublicensable, revocable license to call the API for the sole purpose of (a) evaluating integration on the sandbox tier or (b) fulfilling the use case described in your signed agreement on a paid tier.

We retain all right, title, and interest in and to the API, its responses, the data within them, the schemas, the models that produced them, the methodology, the OpenAPI specification, the developer-portal interface, the documentation, all SplitWinner and SplitWinner trademarks, and all related intellectual property. No rights are granted by implication, estoppel, or otherwise.

3. Restrictions — What You Cannot Do With API Responses

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

  • Scrape, harvest, or systematically extract data — including, without limitation, automated collection beyond your tier's documented use case, parallelised pagination designed to exceed documented rate limits, or any process designed to build a local mirror of SplitWinner data. This applies whether the source is /v1/* paid responses or sandbox synthetic data.
  • Distill, train, fine-tune, or otherwise build any machine-learning model on SplitWinner outputs. This includes using API responses (predictions, confidences, intel, model identifiers, audit hashes, metric snapshots, insight payloads, or any other field) as training data, validation data, evaluation data, or reference labels for any model — yours or a third party's — even if that model would be used internally and never resold. Model distillation on our outputs is the most directly prohibited use of this API.
  • Catalog, index, archive, or republish API responses into any directory, dataset, statistical reference, betting database, prediction archive, anchored-content registry, or analytical product accessible to anyone outside your direct integration. Building a "SplitWinner historical dataset" or "verified-pick catalog" is not permitted at any tier without a separate written agreement.
  • Disclose API responses to any third party outside your direct integration — including the specific values returned, our model identifiers, audit hashes presented in a way that implies endorsement, error messages, response timing characteristics, undocumented field names, or any internal-looking detail observed during integration. Customer-facing surfaces of your paid integration are permitted under the redistribution policy in your MSA; everything else is Confidential Information (Section 4).
  • Resell, sublicense, syndicate, white-label, or redistribute API responses or your API key, as a feed, an embed, a downloadable archive, an API of your own, or in any other form, without a signed agreement that explicitly permits it. This applies to verbatim values, summaries, derived signals, statistical aggregates, and "anonymised" derivatives.
  • Share your API key, key fingerprint, or any credential with any individual or entity other than the company you signed up on behalf of. One key per direct integration. Compromise of a key is your responsibility (Section 4).
  • Reverse-engineer, decompile, disassemble, or attempt to derive the source code, model weights, training data, feature engineering, hyperparameters, or system architecture from any API response, error, latency pattern, or other observable behavior.
  • Probe for security vulnerabilities, attempt to bypass authentication, request signing, rate limits, tier enforcement, IP allowlists, or expiration enforcement, or conduct any form of penetration test without our prior written consent. Good-faith vulnerability disclosure under Section 4 is permitted.
  • Build a competing product using our outputs. This includes — without limitation — training models on our responses (covered above and emphasised here), replicating our prediction or audit-trail shape into a competing feed, embedding our outputs into a product that markets itself as an alternative to SplitWinner, or aggregating our responses into a third-party data product.
  • Misrepresent your relationship with us, falsely claim affiliation, register a domain or trademark confusable with SplitWinner or SplitWinner, or display our marks except as permitted in a separate brand-attribution clause.
  • Use the API in violation of applicable law (including gambling regulations in your jurisdiction) or to facilitate prohibited activity.
  • Permit shared use of a single account or key across multiple individuals or entities except as expressly authorized in a signed agreement.

A breach of any item in this Section 3 is a material breach. We may suspend access immediately and pursue all remedies available under law, including injunctive relief.

4. Security and Confidentiality

  • Your API key is a credential. You will keep it secret, never embed it in client-side or end-user-distributed code, and rotate it promptly on suspected exposure. You are responsible for all activity under your key, including activity by anyone you give the key to.
  • Restrict your keys. The developer portal supports per-key IP allowlists (CIDR) and per-key expirations — we strongly recommend enabling both for production keys. A key without restrictions is your full credential.
  • Non-public information you observe while integrating — including undocumented error patterns, internal identifiers visible in error payloads, rate-limit-bucket behavior, and any details of our infrastructure — is Confidential Information. You will not disclose it publicly.
  • Vulnerability disclosure. If you discover a security vulnerability, report it to security@splitwinner.com. Do not publicly disclose it until we have either fixed it or sixty (60) days have elapsed, whichever comes first. We will not pursue legal action against good-faith research that follows this disclosure policy.

5. Accuracy Disclaimer — No Guarantee of Outcome

EDGESEEKER PREDICTIONS ARE PROBABILISTIC FORECASTS GENERATED BY MACHINE-LEARNING MODELS. THEY ARE NOT GUARANTEES, NOT INVESTMENT ADVICE, NOT BETTING ADVICE, AND NOT FINANCIAL OR LEGAL ADVICE. PAST MODEL PERFORMANCE IS NOT INDICATIVE OF FUTURE RESULTS. SPORTS OUTCOMES ARE INHERENTLY UNCERTAIN.

The API may return outputs that are incorrect, late, incomplete, or inconsistent. We provide the API and all responses "AS IS" and "AS AVAILABLE", without warranty of any kind, express or implied, including warranties of merchantability, fitness for a particular purpose, accuracy, non-infringement, uptime, or that the API will be uninterrupted or error-free.

You are solely responsible for any decision you make using the API and for any losses, including financial losses from sports betting or related activity, resulting from those decisions.

6. Limitation of Liability

To the maximum extent permitted by law:

  • We will not be liable for any indirect, incidental, special, consequential, exemplary, or punitive damages, including lost profits, lost revenue, lost data, lost bets, or business interruption, arising out of or related to the API, even if advised of the possibility of such damages.
  • Our total cumulative liability for all claims arising out of or related to the API, in any form of action (contract, tort, or otherwise), will not exceed the total amount you paid us for the API in the twelve (12) months immediately preceding the event giving rise to the claim. For the sandbox tier, that amount is zero (US$0.00).

Some jurisdictions do not allow exclusion of certain warranties or limitation of liability for consequential damages; in those jurisdictions, the foregoing limitations apply to the maximum extent permitted by law.

7. Indemnification

You will defend, indemnify, and hold harmless SplitWinner, its officers, employees, and contractors from and against any third-party claim, demand, loss, or expense (including reasonable attorneys' fees) arising out of or related to (a) your use of the API, (b) your breach of these terms, (c) your violation of applicable law, or (d) your infringement of any third party's rights.

8. Suspension and Termination

We may suspend or terminate your access to the API, your API key, or your account at any time, with or without notice, for any reason or no reason, including suspected breach of these terms, suspected security risk, or non-payment under a paid tier. On termination:

  • All license grants in Section 2 terminate immediately.
  • Sections 2 (retained rights), 3, 4, 5, 6, 7, and 10 survive.
  • You must cease all use of the API, destroy any cached responses you are not contractually permitted to retain, and delete your API keys.

9. Changes to These Terms

We may update these terms at any time. The current version is always available at splitwinner.com/legal/api-terms. We will make a reasonable effort to notify active customers of material changes by email. Continued use of the API after a change constitutes acceptance of the updated terms.

10. Governing Law and Disputes

These terms are governed by the laws of the State of Delaware, United States, without regard to conflict-of-laws principles. Exclusive jurisdiction and venue for any dispute lies in the state and federal courts located in Delaware, and you consent to personal jurisdiction there. The United Nations Convention on Contracts for the International Sale of Goods does not apply.

11. Contact

  • Legal: legal@splitwinner.com
  • Security: security@splitwinner.com
  • Sales: sales@splitwinner.com
  • Support: support@splitwinner.com

If you are signing up on behalf of a company, you represent that you have authority to bind that company to these terms.

Version history

  • v2 (2026-06-13) — Section 3 expanded with explicit named prohibitions on distillation/training, cataloging/archival, third-party disclosure, and resale of derived signals. Section 4 adds the recommendation to use per-key IP allowlists and expirations.
  • v1 (2026-06-13) — Initial publication.