Filter Trust Rollout Status
Retrieves the certificate rotation status with node-level detail for specific verticals and/or node statuses. This is the primary endpoint for diagnosing rotation failures.
When to use:
Use this endpoint after GET /trust/trust-rollout-status reveals that a rotation has
COMPLETED_WITH_FAILURES or is still IN_ROTATION with pending nodes. Filter by
vertical and status to retrieve the exact list of nodes (with error messages) that
require attention.
Filter Behavior:
vertical_names: Restricts results to the specified verticals. Values must match theTrustRolloutStatusVerticalKeyenum. Obtain valid values fromvertical_keyfields inGET /trust/trust-rollout-status.include_status: Restricts node-level detail to nodes in the specified states (SUCCESS,FAILED,PENDING). Only matching nodes are populated insuccess_nodes,failed_nodes, orpending_nodes.- If the request body is omitted, the response is equivalent to
GET /trust/trust-rollout-status(summary-level data, no node detail).
Important: Node-level detail is only available for certain verticals (e.g.,
BAREMETALSECURITY, SENSOR). Other verticals (NSX, AVI, SSP, LH) always
return empty node arrays - their status is limited to START_SUCCESSFUL or
FAILED_TO_START_ROTATION.
Chaining:
- Call
GET /trust/trust-rollout-statusto identify the overall status and which verticals havefailed_node_count > 0in theirstatus_summary. - Call this endpoint with those vertical keys and
include_status: ["FAILED"]to retrieve node-level error details for remediation.
Notes:
- Returns
400ifvertical_namescontains values not in theTrustRolloutStatusVerticalKeyenum, or ifinclude_statuscontains values outside ofSUCCESS,FAILED,PENDING. - Verticals not matching the filter are excluded entirely from the response.
Show optional properties
{
"vertical_names": [
{}
],
"include_status": [
{}
]
}
{
"vertical_names": [
"string"
],
"include_status": [
"string"
]
}
List of vertical keys to include in the detailed node-level response. Values must
match the TrustRolloutStatusVerticalKey enum. Obtain valid values for the current
deployment from the vertical_key fields in the GET /trust/trust-rollout-status
response. Invalid values cause a 400 response.
List of node rotation statuses to include in the node-level detail arrays.
Only nodes whose update_status matches one of the provided values will be
returned in success_nodes, failed_nodes, or pending_nodes. Invalid values
cause a 400 response.
OK - Returns the certificate rotation status with node-level details for the specified filter.
{
"rollout_type": "string",
"informational_messages": [
"string"
],
"progress_percent": 0,
"vertical_status": [
{
"vertical_key": "string",
"rollout_result": "string",
"status_summary": {
"success_node_count": 0,
"failed_node_count": 0,
"pending_node_count": 0
},
"success_nodes": [
{
"node_display_name": "string",
"node_id": "string",
"error_message": "string",
"update_status": "string"
}
],
"failed_nodes": [
{
"node_display_name": "string",
"node_id": "string",
"error_message": "string",
"update_status": "string"
}
],
"pending_nodes": [
{
"node_display_name": "string",
"node_id": "string",
"error_message": "string",
"update_status": "string"
}
]
}
],
"overall_status": "string",
"start_time": 0
}
Identifies which certificate is being rotated in this workflow run.
PLATFORM_CA- The platform root CA certificate is being renewed and all certificates signed by that CA are being re-issued and distributed across all verticals. Triggered automatically by the platform when the root CA is near expiration, or initiated via the Trust Management UI. This is the most common rotation type.INGRESS- The external-facing ingress (TLS) certificate is being rotated. Initiated via the Trust Management UI only, when a new CA-signed ingress certificate is applied. Affects inbound connections to the SSP platform from external clients.
The active rollout_type is returned in TrustRolloutStatus.rollout_type.
Human-readable log of key events during the rotation workflow, ordered chronologically. Useful for understanding the sequence of steps taken and diagnosing issues. These messages are also visible in the SSP Trust Management UI.
Approximate percentage of the rotation workflow that has completed, ranging from 0 to 100. Updated continuously during an active rotation. This value is an estimate based on both rotation steps and participant node completion counts and may not increase linearly.
Per-vertical breakdown of certificate rotation status. Each entry corresponds to
one platform component (vertical) participating in the rotation. The vertical_key
in each entry is a valid input for vertical_names in the
POST /trust/trust-rollout-status filter request.
The aggregate status of the entire certificate rotation workflow across all participating verticals.
SCHEDULED- Rotation is queued but has not started yet.IN_ROTATION- Rotation is actively in progress; do not callDELETE /trust/trust-rollout-statuswhile in this state.COMPLETED_SUCCESSFULLY- All verticals and all nodes successfully rotated their certificates. Safe to callDELETEto reset.COMPLETED_WITH_FAILURES- The rotation finished but one or more nodes failed. UsePOST /trust/trust-rollout-statuswithinclude_status: ["FAILED"]to retrieve failure details before callingDELETEto reset.
Unix epoch timestamp in milliseconds when the certificate rotation workflow began execution. Use this to correlate rotation events with platform logs.
Bad Request - The filter criteria are malformed. This occurs when:
- A
vertical_namesvalue is not one of the validTrustRolloutStatusVerticalKeyenum values (BAREMETALSECURITY,SENSOR,SSP,LH,NSX,AVI). - An
include_statusvalue is not one ofSUCCESS,FAILED, orPENDING.
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}
HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
Unauthorized
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}
HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
Forbidden
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}
HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
Precondition Failed
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}
HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
Precondition Required
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}
HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
Too Many Requests
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}
HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
curl -X POST -H 'Authorization: <value>' -H 'Content-Type: application/json' -d '{"vertical_names":["string"],"include_status":["string"]}' https://{api_host}/ssp/trust/trust-rollout-status