Export (0) Print
Expand All

Resource Level Operations

Ff751630.note(en-us,MSDN.10).gifNote:
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.

This topic describes the HTTP operations that are supported at the top-level resource level (resources such as Contacts, Profiles, and Activities), and the properties and headers that are common to those operations.

The following URI format is used to access top-level resources. The URI is not case-sensitive.


http[s]://[LocatorID.]apis.live.net/V<Version>/cid-<CID>/<ResourceName>/
  • Version is the Windows Live API Service version number.
  • CID is a unique hexadecimal value that represents a Windows Live user account. The Windows Live API Service assigns this number. CID is used only with Contacts, Profiles, Activities, and Photos.
  • ResourceName is the name of the Windows Live top-level resource that you are accessing, such as Contacts, Profiles, Activities, or Photos.

The following HTTP operation is supported at the resource level.

Operations Description

GET

A GET request on the resource level returns a list of all the collections in that resource.

No properties are used in HTTP operations at the resource level.

The following headers are used in HTTP operations at the resource level. The following are standard HTTP headers unless denoted as custom headers.

GET

Request Headers

Name Values Required/Optional Description

Accept

application/atom+xml

application/rss+xml

application/json

text/xml

Optional

If you do not specify an Accept header, the default format is Atom.

Authorization

WRAP access_token="AuthToken"

Required

AuthToken is an OAuth WRAP authorization token. For information about using OAuth WRAP, see Authorization.

Content-Type

application/atom+xml

application/rss+xml

application/json

text/xml

Optional

Content-Type can be used as a request header or as a response header.

Response Headers

Name Values Description

Content-Location

URI

The URI of the requested content.

Content-Type

application/atom+xml

application/rss+xml

application/json

text/xml

The data format that is used to transfer the content. The default format is Atom Publishing Protocol.

Content-Type can be a request header or a response header.

Cache-Control

no-cache (default)

no-store

The default value is no-cache.

X-HTTP-Live-Request-Id

[RequestID::]

This is a custom header. The server assigns a unique hexadecimal ID to the request. This ID is returned in the response header, and can be used for debugging.

Show:
© 2014 Microsoft