...
Here is a general explanation about possible error codes:
Internal code | HTTP status | Message |
---|
Internal code
HTTP status
Message
1 | 403 | Your membership package has expired or is inactive. For more information, please contact our sales department at sales@statscore.com |
2 | 403 | Invalid credentials. Either the username or the password you provided is incorrect |
3 | 400 | The timestamp parameter you passed is smaller than the allowed minimum limit for this parameter. When getting this error, the <message> element will contains more information about the minimal timestamp allowed. In the event you want all the information since our minimal timestamp, do not pass the timestamp parameter |
4 | 400 | Invalid parameter. The format of the parameter is invalid. For more details about the invalid parameter, see the <message> element |
5 | 429 | You have exceeded the data amount you are allowed. For more information, please contact our sales department at sales@statscore.com |
6 | 500 | Internal error. When getting this error code, please try resending your request, also inform our support team at tech-support@statscore.com so we can fix this problem as soon as possible. |
7 | 403 | Your membership package does not include requested sport |
8 | 403 | Your membership package does not include requested season |
9 | 403 | Your host IP for API connection is invalid. |
10 | 403 | Your subscription has expired or is inactive. For more information, please contact our sales department at sales@statscore.com |
11 | 402 | Your membership package does not include requested method or access to this method has expired |
12 | 404 | The requested resource was not found |
13 | 400 | Invalid parameter. The date_from or date_to parameter is invalid. |
14 | 400 | Required parameter is missing. |
15 | 503 | We are performing scheduled maintenance. We should be back shortly |
Using timestamp
When any request is made, the response contains a timestamp value showing the time of the last generated response.
If you want to receive feed updates rather than refresh the whole feed then you can store this value and use it in your next request. In the documentation of each resource we have included cache times. The cache times need to be considered when calling particular requests.
...