Recommendations for your imports (read interface)
These recommendations concern imports towards you, i.e. the READ interface and display on your website.
1. Local processing vs on-the-fly
Various filters on the data etc. allow you to work with the data on-the-fly, just as you can download the data locally.
We allow both approaches; however, if you want to repeatedly download the whole data package each time, for larger numbers of ads we recommend downloading the data locally to avoid overloading. (We have seen a client who downloaded approx. 10MB of data in every request.)
With local downloading, check before processing the data whether the file is available and contains valid data. Although we strive for the best possible availability, it would be a pity if in such a case you made the data unavailable in your local application.
Request counts are currently not limited, but they are monitored, and we will deal with any excessive load on the server.
2. Working with photos
Either download the photos locally and then use your own generation of the different sizes there, or download the different sizes through our API. OR, in the on-the-fly case, link to our res.tmimg.cz.
We do not recommend linking only to our full-size photos (we have seen a website that used full-resolution photos for 100px thumbnails).
3. Use different detail levels
If you process only some of the data, reduce the volume of processed data with the level ?detail=custom:... (and without listing the sub-agendas you also speed up the generation).
Conversely, if you want whole data packages for lists, you do not have to download them one by one; you can make your work easier with the level ?detail=full and thus download all the data in one step
If, on the other hand, you only need to get the list of manufacturers for a filter on your website, for example, you can use the filter in lists by dealer (we have seen completely unnecessary downloading of all the dealer's data just so that the dealer could load the list of manufacturers)
4. When using pagination, use ?add-row-count=true
Some users send a request for IDs with the complete listing, count it locally and then paginate. For the number of results there is ?add-row-count=true, which returns the number of all matching records.
5. Use lastModified for synchronisation
Where possible, we provide the element lastModified containing the date of the last edit (for photo structures in the stamp tag). Store the time of our last edit and update records only when they change.
6. Use hooks to check for changes
The ideal synchronisation procedure is to implement webhooks and use them for changes. Then, for example once a day (preferably at night), check the data of the latest updates just to be sure (in case some hooks did not arrive). This way you will always have up-to-date data.
