Content Refresh

Content Refresh allows to trigger on-demand content reloads.

Base URL

        https://<consoleFQDN:port>/st/console/api/v1.0/content/refresh

Supported Requests

Input Models

URL Parameters

Name	Type	Description
operationId	String	The unique identifier of the operation.

Example with Sample Response

To check content reload status

GET Request

https://<consoleFQDN:port>/st/console/api/v1.0/content/refresh/1423D0D3-3D7C-4F8A-9A5C-68F6B157D306

Sample Response

─
{
  "state": "Running",
  "success": false,
  "started": "2026-10-09T14:30:00Z",
  "ended": null,
  "summary": "Content refresh in progress",
  "steps": [
    {
      "name": "Download Windows Patch Catalog",
      "status": "Success",
      "started": "2026-10-09T14:30:02Z",
      "ended": "2026-10-09T14:30:15Z",
      "summary": "Downloaded version 2.3.0.0"
    },
    {
      "name": "Download Red Hat Patch Catalog",
      "status": "InProgress",
      "started": "2026-10-09T14:30:16Z",
      "ended": null,
      "summary": null
    }
  ]
}

Requesting a Content Refresh

POST Request

https://<consoleFQDN:port>/st/console/api/v1.0/content/refresh

Sample Response

Body

Status code:
202 Accepted
409 Conflict

Headers

Operation-Location - URL to poll for operation status

Location - URL to retrieve the refresh results

For example:

Copy

HTTP/1.1 202 Accepted
Operation-Location: https://<consoleFQDN:port>/st/console/api/v1.0/operations/1423D0D3-3D7C-4F8A-9A5C-68F6B157D306
Location: https://<consoleFQDN:port>/st/console/api/v1.0/content/refresh/1423D0D3-3D7C-4F8A-9A5C-68F6B157D306

Important Notes

• A 202 Accepted response means that the content refresh is queued, not completed.
• Poll the refresh status to verify that the content refresh is complete.
• Only one content refresh can run at a time for each service instance.
• If a content refresh is already in progress, the request returns a 409 Conflict response.