Live SDK v5.4 is now available for download. New additions to this version of the SDK include:
When we shipped the Live Connect API service 5.0 April last year, we included the functionality to allow an app to provision applications on behaves of other developers. This functionality is enabled if the app has permission to use the wl.application and the wl.application_create scope. Application information can be access through the https://apis.live.net/v5.0/me/applications path. After observing the usage pattern of this API for more than a year, we have concluded that this API does not fit into the user model and the design goals of the Live Connect API, whose primary objective is to provide developer access to user’s data stored in Windows services, not a platform to auto provision applications. With that, we’re now announcing the plan to decommission any APIs that are related to application provisioning through the Live Connect API service, which include all calls to the https://apis.live.net/v5.0/me/applications path and its sub-paths. These APIs will stop working in March 2013.
With the release of v5.0 of the Messenger Connect API, the previous version is now deprecated. As mentioned in the v5.0 announcement blog post, the latest version of the Messenger Connect API is the result of taking into account a lot of the input from developers about how to simplify the API and address key limitations we had in the previous version.
The v4.1 API will continue to function and will be supported for one year after the release of the v5.0 API. New applications are strongly encouraged to use the v5.0 Messenger Connect instead of the deprecated v4.1 API. It is also recommended that when you upgrade or modify existing applications avoid using and remove usage of the v4.1 APIs.
Below is a list of v4.1 features that will no longer be supported in new applications with the release of v5.0 of the Messenger Connect API
In summary, the v4.1 Messenger Connect APIs are deprecated and ceased working on August 14, 2012.
Last year, we announced that support for Messenger will end in 2013. Apps that already use Extensible Messages and Presence Protocol (XMPP) will continue to be supported until October 2013. We strongly discourage any new implementations relying on XMPP. Instead, we encourage you to learn more about our APIs for SkyDrive, Hotmail and Skype at http://dev.live.com.
The documentation for XMPP and messaging has been removed from the Windows Dev Center and archived. This info will not be updated and might contain links to content that no longer exists. But you can still find the XMPP topics here if you need them:
We’ve also added the following new features in the REST API as highlighted in this SkyDrive blog post.
If you're developing apps for other platforms, you don't need to download the Live SDK; you can reference our updated Representational State Transfer (REST) API directly, as follows:
If you have any questions about these downloads or about the Live SDKs in general, post them in this forum. We have team members here that are ready to help you.
This forum is monitored by Live Connect Support and Product Group team.
Hours of Operation: 8:00AM – 5:00PM US Pacific Time (Monday – Friday)
We do not provide any support over the weekend (Saturday-Sunday).
Live Connect Support Team
We would like to inform you of about the changes to the OAuth 2.0 SDK. We have transitioned the OAuth endpoints to https://login.live.com. This change is to move our OAuth 2.0 authentication service to be on the same backend as our primary login infrastructure. It will give increased scalability and reliability to our OAuth interface and also add some security features like invalidating refresh tokens if the users are detected as compromised or has changed their password.
The https://oauth.live.com endpoints will continue to function but with slightly increased latency so we recommend you begin using the new URL’s.
The new endpoints are:
The old end points are:
Live SDK v5.3 is now available for download here. New additions to this version of the SDK include:
SkyDrive REST API enhancements - we have added the ability to search for files in a user’s SkyDrive by using a partial file name. You can do this by simply making an HTTP GET call with the search parameter 'q'. Here is an example:
The response contains the list of files that have “expenses” in the file name.