TL;DR
A strong recommendation going forward, each client of the API should identify itself by using a unique and descriptive User-Agent string.
The ZXInfo API has been updated, you can find more information and try out yourself in the documentation found here: ZXInfo V3
Going forward the previous version changes status to deprecated, which means it will no longer be update - and you can expect it to close down in 6 months time from today. I believe this timeframe is sufficient for every client to upgrade using v3.
What is ZXInfo API?
This API makes it possible to access ZXDB information, making it possible to build other types of apps without the need to understand the SQL structure of ZXDB, installing required software such as SQL database and having to maintain your own running instance of ZXDB. With this you can easily integrate ZXDB in your own programs, from simple lookup to full featured websites such as ZXInfo or apps like Zx App.
What's new?
The main changes are done to the JSON format returned by the API
- cleanup and better structure around elements returning array/list
- added more information, such as new relations introduced in ZXDB during time
- added back magazine references
A new endpoint to get list of entries based on starting letter has been added.
- /games/byletter/{letter}
The web site ZXInfo has been switched to the use the new V3 API, and some other clients has been testing as well. (You know who you are
![Wink ;)](./images/smilies/icon_e_wink.gif)
As always I'm open for discussion of future requirements of ZXInfo API, as I believe that community driven effort will make this the best API for accessing ZXDB data.