🔐Authentication
All of our API's require authentication. You can create API tokens in MySportmonks.
To make our first request, we’ll need to get authenticated first.
We offer two different options for passing your API token. You are free to choose between the authentication methods. You can also use both of them at the same time. Please note that both methods count towards the same rate-limiting.
Authenticate using a query parameter You can pass your API token by passing 'api_token' in your request parameters, like so:
https://api3.sportmonks.com/api/v3/football/livescores?api_token=your_token_here
Authenticate using a request header You can also pass your token via an 'Authorization' header, like so:
Authorization
your_token_here
You can obtain and manage your API token in Mysportmonks. The API token is only meant for your eyes and, as such, should be stored away safely. Our tokens have no expiration date and will remain valid until you manually delete them yourself.
When making a request, a code response will always be returned. The following are all possible HTTP response codes for any request made to the API:
200: OK
Request succeeded
400: Bad Request
It seems that some part of the request is malformed. The exact reason is returned in the response.
401: Unauthorized
The request is not authenticated.
403: Forbidden
Not authorized. Indicates you're attempting to access a feed that is not accessible from your plan.
429: Too Many Requests
Too many requests. In order to make the API as responsive as possible, you have an hourly request limit. The limit for your current subscription can be found in any successful response. Check the "meta" section to find out your limit.
500: Internal Server Error
An internal error has occurred and has been logged for further inspection. Please email support if you are receiving this error.
Last updated