Provisioning

Introducing the Unified Communications Web API (UCWA)


The Unified Communications Web API (UCWA) is a new REST-like API to enable real-time communications over the web on Server-Side based works for Microsoft Lync on-primes and it is not supported for Office 365 till now.

The new UC Web API, or UCWA, in Microsoft Lync Server 2013 opens a new way of integration with many other client platforms. Lync Server 2013 UCWA brings Lync functionality to desktop applications, web applications and embedded devices with no need for Microsoft Lync client being installed and without Server side component either.

As you could remember with Lync 2010 if you want to create a client application for desktop or PCs you should use the Lync 2010 SDK and host it in any type of user interface like WPF or Silverlight also if you want to create and Add-Ons for the Microsoft Lync Server you need to use the UCMA but now UCWA makes customizations possible on any platform, device or application that can talk http and no browser plugin or ActiveX or Lync client is required with UCWA.

Features of the Unified Communications Web API (UCWA)

  • UCWA removes programming language dependencies.
  • No browser plugin required and No ActiveX dependency.
  • Lync client does not need to be running.
  • Built on top of UCMA.
  • REST-like API to create and work.
  • Simple data structures.
  • Embrace HTTP as an application layer.
  • Resource-oriented programming model.

What Developers Could Do and Access Using UCWA

  • Presence
  • Group Memberships
  • Contacts
  • Privacy Relationships
  • Scheduled Conferences
  • Search
  • Instant Messaging

What Developers Could Do and Access Using UCWA

  • No Audio, Video and any other media
  • No Conferencing only User level interaction
  • No Application Sharing

OAuth Token

The cool thing with the UCWA it Attempt to locate Autodiscover service and the Requested is redirected to OAuth endpoint to get a token and we have the features of the OAuth i.e. provide user credentials, Token is attached to every request header and Token establishes the user’s identity.

The (Representational State Transfer) REST has an Architectural pattern that sees the internet as a collection of resources available at unique locations (URLs\HREFs) so this approach is very great to enable us to create different types and models of applications for different platforms i.e. Linux Lync Client, Web Chat Lync client and Add Instant Message or Presence capabilities to any embedded device that can do HTTP.