200

OK

The GET request successfully executed without error.

201

Created

The POST request successfully executed without error.

204

No Content

The UPDATE or DELETE request successfully executed without error.

206

Partial Content

Only part of the HTTP/1.1 request succeeded. This response is only provided when the GET request is at the root level, and the DeltaSync header is set to "Basic."

304

Not Modified

The data requested in the GET request has not been modified since the timestamp supplied in the request.

400

Bad Request

The request cannot be executed because the request fails to comply with the required format. For example, the request contains invalid Enum values or the request attempts to update read-only values.

401

Unauthorized

The caller is not authorized to perform this action on the target address book.

401

Unauthorized

Invalid CallerID, Missing CallerID value or the Family Safety Assertion failed.

403

Forbidden

Exceeded the maximum number of inserted objects. (See Windows Live Contacts API Reference: Quotas and Limits.)

403

Forbidden

The server understood the request but refuses to fulfill it. Authorization will not help, and the request should not be repeated. This error is returned if a method is requested but not supported.

404

Not Found

The URI does not point to a valid resource. For example, the ContactID is not valid.

405

Method Not Allowed

The method that is specified in the Request-Line message is not allowed for the resource that is identified by the Request-URI field. The response includes an Allow header that contains a list of valid methods for the requested resource.

This error code is returned if a request attempts to POST or DELETE on a singleton property. For example, this status code is returned when a DELETE request is made on a "…/owner" URI or a POST request is made on a "…/FirstName" URI. Windows Live Contacts will respond with “Allow = GET, PUT” in this case.

If any method other than POST, PUT, GET, and DELETE are requested, Windows Live Contacts will respond with "Allow=POST, PUT, GET, DELETE".

409

Conflict

The request could not be completed due to a conflict with the current state of the resource. This error code indicates errors related to unique key conflicts in Windows Live Contacts.

412

Precondition Failed

Error response to an If-Unmodified-Since header if the database record has a newer time stamp than the time stamp supplied in the PUT request.

500

Internal Server Error

Unexpected failure during request processing.

503

Service Unavailable

Returned to all applications for the same reasons as in Error Code 504, but indicates that no services are available.

504

GatewayTimeOut

This may be sent instead of the "503:Service Unavailable" status code. This indicates that only the Windows Live Contacts service is unavailable, instead of indicating that all services are unavailable.

This status code may be returned when the server is currently unable to handle the request due to a temporary overloading or server maintenance.

This is a temporary condition that will be alleviated after some delay. If the length of the delay is known, the length may be indicated in a Retry-After header of the response.

If no Retry-After header is provided in the response, the client must handle the response as it would for a "500 Internal Server Error" status code response.

This code is also used if the caller is throttled after reaching the method calls-per-second quota.