Recently we’ve been inserting some new functionality into Tr@veller Lite.  Alongside that we’ve also been looking at giving it a distinctively different look and feel to the existing Tr@veller product. 

As yesterday I only covered one command, I’ll cover two today instead.  So far I’ve covered two commands, the Search  and Property commands, today I will be focusing on the Price command. The price command a more detailed breakdown of a properties price than the Search command provides, as well as detailing its extras. These extras can include both optional and compulsory extras.

Another post about the AcuWeb API, since I missed posting one yesterday there will be two today. The first command I’m going to focus on today is the Property Command, more details about the request/response can be found within the AcuWeb API, but I hope to give a general overview as to how this command can be used. For more details on AcuWeb API and the search message see my previous post.

We’ve been working hard behind the scenes on AcuWeb and getting it ready to roll out as soon as we can, but a lot of the work so far has been laying the groundwork to support the degree of flexibility to websites and the booking engine that we want to provide. At this stage however, everything’s getting tied together and that initial work on backend is really paying off. This week I plan on giving a quick overview of some of the messages and how they can be accessed to give a better idea on how easy AcuWeb is to use.

From this blog I’ll be posting about the progress we make on the backend of the Acumen Website replacement project.  This system is designed to be a centralised interface that will both drive the replacement Acumen websites and also allow clients to access it directly to drive their own websites, where required.