# Notes and Troubleshooting

Follow the below practices and restrictions while working with TRADE360  API

Be advised of the following general limitations for all TRADE360  API:

* Same request – Every 5 Seconds.
* 5 Different requests at the same time.

If stricter limitations are specified, such as for the [Snapshot API](snapshot), they will take precedence over these.

We highly recommend using only filtered requests, otherwise, 'full' requests can take longer to retrieve, and in some cases, you won't be able to retrieve requests at all due to the vast volume of data.

Here are examples of "full" and "filtered" requests

**Full** - [https://stm-snapshot.lsports.eu/PreMatch/GetEvents](https://stm-snapshot.lsports.eu/PreMatch/GetEvents)

```javascript
{
    "PackageId": ,
    "UserName": "",
    "Password": ""
}

```

**Filtered** - [https://stm-snapshot.lsports.eu/PreMatch/GetEvents](https://stm-snapshot.lsports.eu/PreMatch/GetEvents)&#x20;

```javascript
{
    "PackageId": ,
    "UserName": "",
    "Password": "",
    "sports": "",
    "location": ""
}
```

**TRADE360 API data preservation:**

* How long do we keep data available for Prematch? - 24 Hours from the event's final status.
* How long do we keep data available for the Inplay snapshot?  - 24 Hours from the event's final status.

#### Handling Special Characters in GET Requests

When making GET requests via the browser, encoding special characters is important. Failure to do so will result in the request failing. Please ensure that all special characters are properly encoded before sending the request.



{% hint style="info" %}
### Notice on API Timestamp Format

All timestamps are in UTC format, including rare cases without a "Z" indication
{% endhint %}

