Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Here is a general explanation about possible error codes:

Internal code

HTTP status

Message

Internal code

HTTP status

Message

1403

Your membership package has expired or is inactive. For more information, please contact our sales department at sales@statscore.com

2403

Invalid credentials. Either the username or the password you provided is incorrect

3400

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 

4400

Invalid parameter. The format of the parameter is invalid. For more details about the invalid parameter, see the <message> element

5429

You have exceeded the data amount you are allowed. For more information, please contact our sales department at sales@statscore.com

6500

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.

7403Your membership package does not include requested sport
8403Your membership package does not include requested season
9403Your host IP for API connection is invalid.
10403Your subscription has expired or is inactive. For more information, please contact our sales department at sales@statscore.com
11402 Your membership package does not include requested method or access to this method has expired
12404The requested resource was not found
13400Invalid parameter. The date_from or date_to parameter is invalid.
14400Required parameter is missing.
15503We 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.

...