GET
Retrieves the list of EULA records. [tags: DMA]
Request
Response
| Status |
Representation |
Description |
| 200 |
application/vnd.plcm.plcm-eula-list+xml
|
Eula records successfully retrieved. |
| 304 |
|
Eula records have not changed since the last get.
Note: The API client must provide the "plcm-eula-list" 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
search in the "If-None-Match" header, then the HTTP response will contain the
search results in the message body.
The "plcm-eula-list" ETag can be accessed from the initial search result's HTTP
response header. Also, subsequent searches require the identical search filter
to ensure an equivalent ETag value. This also assumes no other client made changes to
the EULA on the server.
|
PUT
Accepts ithis list of EULA record. [tags: DMA]
Request
Representations
Response
| Status |
Representation |
Description |
| 204 |
|
Eula record successfully accepted. |
| 428 |
|
Eula information has changed since the last retrieval.
Note: The response will contain the ETag value and link that reflects
the server's EULA 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-eula.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.
The "plcm-eula" ETag can be accessed from the initial retrieval result's HTTP
response header. Also, subsequent retrievals require the identical eula-identifier
to ensure an equivalent ETag value. This also assumes no other client made changes to
EULA records on the server.
|
| 401 |
application/vnd.plcm.plcm-error+xml
|
User is not authorized to accept the EULA. |
| 406 |
application/vnd.plcm.plcm-error+xml
|
Not Acceptable |
|