Retrieves the schema definitions for all RCC relations.
You can retrieve all RCC relations for a specific incident or change.
To retrieve all RCC relations tied to a specific incident, use the incident_id
and optional include
fields.
To retrieve all RCC relations tied to a specific change, use the change_identifier
and include_history
fields.
Each call should only use either incident_id
or change_identifier
.
The
change_identifier
is a unique identifier from the original change tool. It is not the BigPanda system id. In the BigPanda console, you can find thechange_identifier
under the Key field of the Root Cause Changes table.
Current Suspects & Matches Only
When retrieving RCC relations for a change, if the change is not currently associated with any incidents as a suspect or match, no results will be returned.
Authentication
All BigPanda APIs require Bearer Token Authorization in the call headers.
This API uses the User API Key type of Authorization token.
Sample Calls
curl --request GET \
--url https://api.bigpanda.io/resources/v2.0/rcc?incident_id={incident_id} \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <USER API KEY>'
curl --request GET \
--url https://eu-api.bigpanda.io/resources/v2.0/rcc?incident_id={incident_id} \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <USER API KEY>'
curl --request GET \
--url https://api.bigpanda.io/resources/v2.0/rcc?change_identifier=CHS48476739&include_history=true \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <USER API KEY>'
curl --request GET \
--url https://eu-api.bigpanda.io/resources/v2.0/rcc?change_identifier=CHS48476739&include_history=true \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <USER API KEY>'