Poll for Response to the Request for Manifest File
Poll for a response to the request for the manifest file, using the polling ID returned by a POST to the /uai/2.0/updates/manifests API. It can be used repeatedly until a 200 response is received.
|
Item |
Description |
|
URI |
|
|
Method |
GET |
|
Query parameters |
pollingId: The ID returned in Find Available Updates service. |
|
Request body |
N/A |
|
Response codes |
200: Success 202: Submitted request is still being processed. Use the URL returned to continue to poll for the response. 401: The request is unauthorized. This could be because a JWT was not found in the header, the token has expired, the signature is invalid, or a public key could not be identified (most commonly because the public key has not been uploaded to FlexNet Operations). 410: A response for the polling ID could not be found. This could be a result of using an incorrect polling ID, or of too much time having elapsed, so that the polling ID is no longer valid. |
Sample Response
This is the data structure for a successful response (status 200) to the request for the manifest file:
{
"manifestFiles": [
{
"execute": "string",
"fileSize": "string",
"fileUrl": "string",
"md5Hash": "string",
"sha256Hash": "string"
}
],
"manifestVersion": "string"
}
If the request is still being processed (status 202), a URL to poll for completion of the request is returned:
{
"url": "string"
}
If a response for the polling ID could not be found (status 410), the response body will describe the error, as shown in the following example:
{
"arguments": "string",
"key": "string",
"message": "string"
}