204 |
|
Registration share information successfully updated.
Note: The response will only contain both an ETag value
and link to the updated registration share resource.
|
304 |
|
Registration share information has not changed since the last retrieval.
Note: The API client must provide the "plcm-registration-share" representation's
ETag value in the "If-None-Match" HTTP header to ensure conditional
retrieval. This will improve network performance by reducing bandwidth
consumption.
If the API client chooses to exclude an ETag value from a previous,
identical single registration share retrieval in the "If-None-Match" header, then
the HTTP response will contain the registration share representation in the message
body.
The "plcm-registration-share" ETag can be accessed from the initial retrieval result's HTTP
response header. Also, subsequent retrievals require the identical domain and
user name to ensure an equivalent ETag value. This also assumes no other client made changes to
registration share on the server.
|
401 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
User is not authorized to update the registration share records |
403 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
User has insufficient permissions to perform the operation. |
404 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
No such registration share |
412 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
The registration share resource has changed on the server.
Note: The response will contain the ETag value and link that reflects
the server's registration share resource in the HTTP response header.
The API client must supply the ETag in the message body that is bounded by
the "entity-tag" XML tag. Refer to the "plcm-registration-share.xsd" for details.
If the message body does not contain the ETag value, the server will
look for the ETag in the "If-Match" header.
|
428 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
The API client must supply the ETag in the message body that is bounded by
the "entity-tag" XML tag. Refer to the "plcm-registration-share.xsd" for details.
If the message body does not contain the ETag value, the server will
look for the ETag in the "If-Match" header.
|