Libraries and Controls
|Current information about Live Connect is now available in the Windows Live Developer Center. The information in the following sections is provided for legacy purposes only.|
Windows Live Messenger Connect provides a variety of ways to integrate your applications. You can use Messenger Connect on your website and in desktop applications (with Windows Presentation Foundation and other technologies).
You can choose from several different types of integration, each covering a variety of scenarios. Your choices include:
Messenger Connect Representational State Transfer (REST) API service.
The typical usage pattern for the Messenger Connect REST API service is as follows:
Request the user's consent to use his or her data that is stored with Windows Live. To do this, you send the user through the Messenger Connect consent user interface (UI). You then receive an access token and a refresh token with which to access the user's data. You can store the refresh token in your database for later use; it is valid for 12 months, whereas the access token is valid for only four hours.
Invoke the REST API for the resource that you are interested in, along with the access token that you obtained.
Use the refresh token to obtain a new access token as needed.
Add the Application Control to your webpage. This control provides Windows Live with information such as your application's client ID, the path for your OAuth WRAP callback handler, and the scope that indicates the resources for which your application is requesting user consent.