We are now caching xml’s on the server in order to limit the number of database queries made through the API. This won’t affect the transfer of data from Zoo Property to your client’s websites as our solution still results in the most optimal transfer of data.

How it works:
There is xml for each of the property status so for Available & Under Offer, Sold & Leased, Withdrawn which looks something like this http://api.agentaccount.com/api/properties?office_id=1&page=1. This xml will show ALL listings with that status if you execute it.  The xml created will be cached on the server for 4 weeks.

This means when you execute the url again the xml already created will be displayed in your browser.

There is another xml which will show any listings updated in the past 30 minutes. The link to this xml will be something like this http://api.agentaccount.com/api/properties?office_id=1&updated.

This xml will be cached on the server for 15 minutes meaning if you execute it after the 15 minutes it will scan the database and display the fresh results.

So what does all of this mean? You need to setup a cron job on your server to execute a scan of the updated xml every 15 minutes. Once this is working you then can perform a scan of the other xmls (containing all listings in the database) which will bring your local database to date. Moving forward any updates in Zoo Property will be sucked in to your local database every 15 minutes.