The term "Web service" describes a standardized way of integrating Web-based applications using the XML, SOAP, WSDL and UDDI open standards over an Internet Protocol backbone. XML is the data format used to contain the data and provide metadata around it, SOAP is used to transfer the data, WSDL is used for describing the services available and UDDI lists what services are available.

A Web service is a method of communication between two electronic devices over a network. It is a software function provided at a network address over the Web with the service always-on as in the concept of utility computing.

In practice, a web service commonly provides an object-oriented Web-based interface to a database server, utilized for example by another Web server, or by a mobile app, that provides a user interface to the end-user. Many organizations that provide data in formatted HTML pages will also provide that data on their server as XML or JSON, often through a Web service to allow syndication.

On this training we will learn how interacting with Avaya IPOffice Server or the Avaya OneCloud CPaaS to perform all of your telephony needs is as simple as visiting a website. You will understand how REST is useful when developing with Avaya Products. With so many possibilities and mash-up ideas, the sky is the limit to the things you can do using Avaya IPOffice Server Platform and the Avaya OneCloud CPaaS's REST functionalities. Avaya REST API can initiate calls, record phone calls, buy phone numbers, send SMS messages, get detailed information about account activity, create conference calls, and much more! Dive into our training to learn about all of the capabilities of Avaya RESTfull Web Services can provide.

The Avaya IP Office Server with Centralized CTI Web Services API introduced in IP Office Release 10.1 offers an open platform for use by developers in creating applications that employ telephony features and other functionalities provided by IP Office such as Call Log, Directory, Instant Messaging, Presence and Voicemail services. The API is supported for use in a distributed IP Office environment and is not limited to use on a nodal basis, as is the current TAPI SDK. This new API has a dependency on Avaya one-X Portal, thus users will require access to the one-X Portal application.