Archive for the ‘Developer System Updates’ Category
Posted on June 29, 2011 • by Team Zoo • Make a Comment »
Previously the page title for the developers and agents system was Zoo Property. This wasn’t ideal for other web developers or network groups using the system as it meant the Zoo Property branding will appear. We’ve since changed this so the title for the systems is the Developer’s name.
eg the Developer’s system for Agentpoint can be found here http://agentpoint.agentaccount.com you will see the system is called Agentpoint (the developers name) rather than Zoo Property. This is the same for all Developers and now means you can fully white label the Zoo Property product.
Posted on June 22, 2011 • by Team Zoo • 1 Comment »
We’ve recently updated the Dashboard in the Developer’s System making it more intuitive for web developers and head office teams to use and manage their clients.
The new look runs through the key areas of the system outlining what each section does and what’s required to get you up and running. The reason these updates were performed was due to constructive feedback from our users. We strive to have a system which is easy to use to and meets the needs of all of our clients.
Thanks for you feedback guys and please feel free to post further comments for improvements.
Posted on January 30, 2011 • by Team Zoo • Make a Comment »
Late in 2010 we deployed a new data API for sending property, team member and office data to agent’s websites. There were bugs to iron out and now the API has been deployed across all sites and is working very well.
Unlike the original API which was XML and pull based, the new API uses HTTP meaning data is automatically pushed to 3rd party sites once it is updated. This means data appears a lot quicker on 3rd party sites and it is also 100% accurate because we receive a success response back from 3rd parties once the data has successfully parsed. There could be issues if the 3rd party server was offline or the cron was not set to read the XML every 15 minutes.
You can check out more about the HTTP API or download the WordPress HTTP API plugin. Note: we encourage web developers to post any support related questions through the API posts (in the links on this post) so we will answer them as quickly as possible.
Posted on January 13, 2011 • by Team Zoo • Make a Comment »
There will be scheduled maintenance at 7.00pm today (13/1/2011) to the Zoo Property system. We plan for the system to be off line for around 10 minutes as we perform a very important upgrade.
We apologise for any inconvenience this may cause.
Regards
Zoo Support
Posted on April 29, 2010 • by Ryan O'Grady • Make a Comment »
There are now enough clients offering property owners and vendors the ability to login to Zoo Property and to add and update their property listings. These clients include private selling websites and agent assisted or owner assisted real estate sales websites who offer a service which involves the property owners.
We have modified the system and created an extra Level (Level 4) for property vendors. Vendors can login to the system and update their listing. In the developer’s system you can set whether or not the listing saves as a draft each time it is added/updated by a vendor. This allows the agent to monitor what updates vendors have made and approve these updates before they filter out to 3rd party websites and real estate portals.
You can opt for this additional functionailty when you are setting up the office in the Developer’s System. Note: There are additional charges for this service.
Posted on April 25, 2010 • by Ryan O'Grady • Make a Comment »
By popular request we have added a feature in the team member section of Zoo Property which allows agents to upload their vCard’s (wikipedia) to the system. These vCard’s are then displayed in the team member xml (in the API) so developers can populate this information on the offices website.
We also added a dropdown in the team members section which allows each team member to be assigned to a specific group eg Property Manger, Executive etc. A few developers were saying it would be ideal if we could group agents allowing them to display agents in groups on the office website.
vCard is a file format standard for electronic business cards. vCards are often attached to e-mail messages, but can be exchanged in other ways, such as on the World Wide Web. They can contain name and address information, phone numbers, e-mail addresses , URLs, logos, photographs, and even audio clips. (Source Wikipedia)
Posted on March 9, 2010 • by Ryan O'Grady • Make a Comment »
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.
Posted on January 1, 2010 • by Ryan O'Grady • Make a Comment »
If you are currently using the developer system and have any ideas in relation to how we can improve this then please feel free to post a comment on this thread telling us what would make your life easier.
We can’t promise it will be implemented but we will certainly consider it and definitely get back to you about it.
Posted on January 1, 2010 • by Ryan O'Grady • Make a Comment »
Previously there was only an API for each office in Zoo Property. We have now enhanced this for web developers by adjusting the API so now xml’s are available for the CLIENT (all offices for that client) and for the DEVELOPER (so all offices and clients belonging to the developer).
The CLIENT XML will come in handy if the developer needs to build a website for multiple offices and wants an easy way to populate the website through 1 xml.
With the developer xml you can display ALL listings belonging to all of your clients in the 1 xml. This will come in handy if the developer needs to populate all of their client’s listings on the one website.
