This is the page for the questions that come up before anyone signs anything. How sports data is collected and checked, what happens when a number is wrong, how we handle personal data under GDPR, how the API is monitored, and what our terms actually allow you to build.
You do not need a call to read any of it. Where we cannot answer something in public yet, we say so on this page and tell you who to ask instead. Questions sent to our support team get a median first reply in under two hours during working hours, from a named person.
Sportmonks B.V., the Netherlands KvK 74390856 EU established, GDPR applies Page last reviewed August 2026
99.99%
Uptime
Measured, published with incident history
6.4B
Requests per month
Roughly 2,400 every second
~15 sec
Live data latency
Typical event to API, faster than broadcast
2,200+
Football leagues
Plus cricket and Formula 1
< 2 hrs
Median first reply
Support runs 7 days a week, working hours CET
2016
Operating since
Ten unbroken seasons of live data
Most providers in this category will not tell you this part. We think it belongs on a page about integrity, because the difference between a good data partner and a bad one only shows up when something is wrong at 20:47 on a Saturday.
01
Our own worldwide scout network covers matches as they happen through our internal Scout Platform, alongside specialist data partners for specific feeds.
02
Incoming data is checked and reconciled by people, not only by scripts. Any discrepancies will be resolved before it reaches your application.
03
We calculate our own metrics on top of the raw data: xG, Pressure Index, predictions and expected lineups. Built in house, so we can explain them and correct them.
04
Everything ships through one REST API in a consistent shape. We run continuous live API and page tests from multiple locations, and publish the result.
Some of what we sell is collected by us. Some comes from specialist partners: our odds feed, for example, is delivered in collaboration with TXODDS. We will tell you which is which for any data point you ask about, because knowing the provenance is part of your own compliance work.
We do not claim to hold official rights on behalf of leagues or competitions, and we do not present partner data as our own collection. Coverage detail sits on the coverage pages.
Images that reach you through the API are convenience, not a licence. Our terms of service put the responsibility on you to hold your own rights for any logo or profile photo you display, or to use your own variation instead.
If you are building something commercial and public facing, treat that as a real line item in your legal review rather than an afterthought.
No sports data feed is right every single time, and our terms of service do not pretend otherwise: we do not guarantee completeness or accuracy at all times. Any provider claiming they do is telling you something about their honesty, not their data.
So the promise worth making is the other one. Here is exactly what happens when you tell us something looks wrong, and who is on the other end when you do.
"Data reliability has been constantly improving. I particularly highlight the support team's agility and efficiency in resolving any issues."
"Once you start utilising it, you realise that its excellence isn't just superficial, the quality of the data itself stands out."
Email [email protected], or go straight to your personal contact if you are on a paid plan. The fastest report includes the fixture or entity ID, the endpoint you called, what you saw and what you expected. Median first reply is under two hours in working hours, 7 days a week.
Every value has a provenance: our own collection, or a named partner feed. That determines who can fix it and how quickly, and we will tell you which one it is rather than leaving you guessing.
Corrections are made in the data itself, so the fix reaches every customer and the historical record, not just the person who complained.
You get an answer from a named person explaining what was wrong, what was changed, and whether anything else you depend on was affected. Not a ticket number closing itself.
We are a Dutch company, established in the EU, so GDPR applies to us directly rather than by choice. Everything below is what our privacy policy commits to, summarised so your reviewer does not have to read the whole thing to find it.
What we process
Your account data: name, email address, address details, login information, and browsing activity through cookies.
Payment details
Card information is encrypted in transit over SSL and handled by a PCI Level 1 service provider. We are not the ones storing your card number.
How long we keep it
While you are a customer. After you cancel, personal information is removed within the applicable legal time frame.
Your rights
Access and correct your details yourself in your account settings, and request access or erasure by email at any time. Both are set out in the privacy policy.
If something goes wrong
In the event of a data breach affecting your personal data, we commit to notifying affected users by email within 7 business days.
Processing terms
A data processing agreement is available on request. Email [email protected] or ask your named contact, and it goes to the person who can send it rather than into a queue.
We would rather you read our real position here than get a polished answer to a questionnaire six weeks into an evaluation.
API traffic and sensitive information are encrypted in transit over SSL and TLS. Payment data is handled by a PCI Level 1 service provider, so card numbers do not sit with us.
Privacy policy →Access is by API token, provisioned instantly at signup and tied to your account. You generate and replace your own tokens in my.sportmonks without asking us. Tokens are the credential, so how you store them matters as much as how we issue them.
See the integration checklist →We run continuous live API and web page tests from multiple locations and measure response times, so degradation is visible to us and to you at the same time.
Live status →We do not hold SOC 2 or ISO 27001 certification today, and we will not imply otherwise on a page about integrity. What we do instead: answer your security questionnaire directly, with a named person, in days rather than quarters. Median first reply to any support question is under two hours.
Send us your questionnaire →The full detail is in the terms of service and the terms are what govern. This is the short version, so you can check your plan against it in a minute instead of a meeting.
Go ahead
Not without talking to us first
Plenty of our customers build betting and trading products, and we supply odds and prediction data for exactly that. What we do not supply is your licence. Gambling regulation, age verification, responsible-gambling duties and market eligibility sit with you in every jurisdiction you operate in.
Our predictions are model output, not advice. The terms state plainly that Sportmonks is not responsible for winnings made or losses suffered on third party sites and applications.
You are welcome to say your product is powered by Sportmonks data, and most of our customers do. Describe the relationship as it is: we are your data provider, not an official rights holder for the competitions covered.
If you want to write something more specific, send us the wording and we will check it. That takes a day, and it is cheaper than a correction later.
There is no contract and no notice period. You change leagues, upgrade, downgrade, add or remove add-ons and cancel yourself in my.sportmonks, without asking us and without a retention call.
Worth saying on a page like this: a vendor that makes leaving difficult is telling you something about how confident it is in the rest of the relationship.
Our uptime is 99.99% and we publish it with the incident history attached, which is the only version of an uptime claim worth reading. It is a measured figure, not a contractual guarantee: if you need a contractual availability commitment, that belongs in an agreement and we will talk about it there.
Detect
Continuous live API and page tests run from multiple locations, measuring availability and response time rather than waiting for reports.
Publish
Disruptions, investigations and planned maintenance are posted publicly on status.sportmonks.com while they are happening, not afterwards.
Notify
Where an incident affects your data or your account, you get told. For a breach of personal data our privacy policy commits to email within 7 business days.
Close out
Our team identifies the cause, restores service and explains what was done. If a validation or collection gap caused it, that gets fixed too, not just the symptom.
If you have found a security issue in our API, dashboard or website, email [email protected] with enough detail to reproduce it. Reports are handled confidentially and with priority. Median first reply across all support email is under two hours in working hours, 7 days a week, and it comes from a named person rather than an auto-reply.
Please do not test against other customers' accounts or data, and give us a reasonable window to fix an issue before publishing it.
The status portal is public and does not need an account: read the incident history for the last months and judge for yourself. It is deliberately the least flattering page we own.
Open status.sportmonks.com or read how the monitoring works on the API status page.
Six things worth doing on your side, whether this is your first API integration or your fiftieth. None of them take long, and all of them are easier to do now than after a token has leaked.
Call our API from your backend, not from browser or mobile client code. Anything shipped to a device can be read off it, and a token in a public repository or a JavaScript bundle is a token someone else now has.
Load the token from an environment variable or a secrets manager, keep it out of version control, and use separate tokens for development, staging and production so you can revoke one without breaking the others.
Generate a new token and retire the old one when someone leaves, when a contractor finishes, or if you are ever unsure where a token has been. You do that yourself in my.sportmonks, and we will help you sequence it with zero downtime if you ask.
Handle 429 responses with exponential backoff rather than an immediate retry loop, and cache what does not change every second. Current limits are documented in the API docs.
Log request volume and error rates on your side, and alert on a sudden jump. Unexpected traffic is usually a retry bug, but it is also the first sign of a leaked token, and you will spot it long before we can.
The request URL with the token removed, the response you got including the HTTP code, what you expected in one sentence, the fixture, league or player ID, when it started, and your account email. That is the difference between an answer and a thread.
There is no ticket queue behind these addresses and no chatbot deciding whether your question deserves a human. Support runs 7 days a week, and customers on a paid plan have a named contact who already knows what they are building.
A score, a stat, a lineup, a missing fixture. Include the entity or fixture ID and the endpoint you called.
[email protected]Suspected breach, exposed token, or something you found while testing your own integration. Handled confidentially and with priority.
[email protected]Access or erasure requests, a data processing agreement, and anything your privacy officer needs from us in writing.
[email protected]Redistribution approval, security questionnaires, contractual availability commitments and entity details. Invoicing goes to [email protected].
[email protected]Account control sits with you, in my.sportmonks, without a call and without a retention conversation:
Being straight about the limits: support is 7 days a week, not 24/7, and the team works in Central European Time. Outside those hours the status page keeps reporting whether the problem is ours, which is usually the question you actually need answered at 02:00.
Legal entity
Sportmonks B.V., a private company registered in the Netherlands
Chamber of Commerce (KvK)
74390856
Registered address
Papenstraat 26, 7411 ND Deventer, the Netherlands
Governing documents
Answered here so you do not have to wait for a call to find out. If your reviewer needs any of this in writing on letterhead, ask and you will get it.
No to all three on our standard plans. You upgrade, downgrade, change which leagues you cover, add or remove add-ons and cancel yourself in my.sportmonks, without contacting anyone and without a retention call.
Enterprise agreements with negotiated terms are a separate conversation, and if you need one you will know it. Everyone else can leave the month they decide to.
Not as raw data without our written approval. You can build products on the data, charge for them, and show the data to your own users. Reselling or redistributing the feed itself needs approval first.
It is a normal commercial conversation rather than a refusal, so if redistribution is part of your model, raise it early and we will tell you what is possible.
Yes. Storing, transferring and distributing the data inside your own product is explicitly permitted by our terms of service, including caching it in your own database. Most customers do exactly that.
No, and we will not imply that we do. We collect data through our own worldwide scout network and work with specialist data partners for certain feeds. We are your data provider, not an official rights holder acting on behalf of a competition.
If your product needs officially licensed data for a specific competition, that is a separate arrangement with that competition, and we would rather say so up front.
None. We never receive data about your end users. The only personal data we process is your own account information: name, email address, address details, login information and cookie data, as set out in our privacy policy.
Where our data describes players and coaches, it is professional career information about public figures. It is still personal data under GDPR and still needs a lawful basis on your side.
Yes, and many of our customers do. We supply odds and prediction data for exactly that purpose. What we do not supply is your gambling licence: regulation, age verification, responsible-gambling duties and market eligibility remain your responsibility in every jurisdiction you operate in.
Our predictions are model output, not advice. Our terms state that Sportmonks is not responsible for winnings made or losses suffered on third party sites and applications.
Email [email protected] with the fixture or entity ID, the endpoint you called, what you saw and what you expected, or go straight to your named contact if you are on a paid plan. We trace it back to the source, correct it in the data rather than patching your response, and tell you what happened.
Send it over. You will get an answer from a named person, not a form response, and if the answer is "we cannot do that" you will get that too.
Median first reply under 2 hours · Support 7 days a week · No contracts, no notice periods · Public pricing and public status