List domain attack paths details
Changed onLists detailed data about attack paths for a domain.
Note: ImpactCount, ImpactPercentage, ExposureCount, ExposurePercentage and Severity will have a value other than zero when butterfly analysis is enabled.
Request
- Base URL: / (relative, and the document was published on a file host, not at the API’s origin)
- URL: /api/v2/domains/{domain_id}/details
- Auth: one of:
- HTTP bearer
- API key in header Authorization and API key in header RequestDate and API key in header Signature
Query parameters
Filter results by column string value. Valid filter predicates are eq, ~eq, neq.
Media type to determine the response format (application/json or text/csv).
Filter results by column string value. Valid filter predicates are eq, ~eq, neq.
Sort by column. Can be used multiple times; prepend a hyphen for descending order. See parameter description for details about which columns are sortable.
Sortable columns are domain_sid, index, AcceptedUntil, id, created_at, updated_at, deleted_at, exposure_percentage, impact_percentage. Relationship risks can be sorted on FromPrincipal and ToPrincipal in addition to the sortable columns for List Risks.
Filter results by column string value. Valid filter predicates are eq, ~eq, neq.
Filter results by column string value. Valid filter predicates are eq, ~eq, neq.
Filter results by column string value. Valid filter predicates are eq, ~eq, neq.
Filter results by column string value. Valid filter predicates are eq, ~eq, neq.
Filter results by column string value. Valid filter predicates are eq, ~eq, neq.
Filter results by column string value. Valid filter predicates are eq, ~eq, neq.
Filter results by column timestamp value formatted as an RFC-3339 string. Valid filter predicates are eq, neq, gt, gte, lt, lte.
Filter results by column timestamp value formatted as an RFC-3339 string. Valid filter predicates are eq, neq, gt, gte, lt, lte.
Filter results by column string value. Valid filter predicates are eq, ~eq, neq.
Filter results by column string value. Valid filter predicates are eq, ~eq, neq.
Filter results by column integer value. Valid filter predicates are eq, neq, gt, gte, lt, lte.
Filter results by column timestamp value formatted as an RFC-3339 string. Valid filter predicates are eq, neq, gt, gte, lt, lte.
Filter results by created_at value. See filter schema details for valid predicates.
Filter results by column timestamp value formatted as an RFC-3339 string. Valid filter predicates are eq, neq, gt, gte, lt, lte.
Filter results by updated_at value. See filter schema details for valid predicates.
Filter results by column timestamp value formatted as an RFC-3339 string. Valid filter predicates are eq, neq, gt, gte, lt, lte.
Filter results by deleted_at value. See filter schema details for valid predicates.
The number of items to skip in a paginated response.
This query parameter is used for determining the number of objects to skip in pagination.
The limit of results requested by the client.
This query parameter is used for setting an upper limit of objects returned in paginated responses.
Response
OK
Changes
- info
added
subschema #1subschema #2to the response bodyanyOflist for the response status - info
removed
subschema #1subschema #2from the response bodyoneOflist for the response status
- info
- breaking
added the pattern
^((eq|neq|gt|gte|lt|lte):)?-?[0-9]+$to thequeryrequest parameterid - breaking
added the pattern
^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$to thequeryrequest parameterAcceptedUntil - breaking
added the pattern
^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$to thequeryrequest parameteraccepted_until - breaking
added the pattern
^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$to thequeryrequest parametercreated_at - breaking
added the pattern
^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$to thequeryrequest parameterdeleted_at - breaking
added the pattern
^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$to thequeryrequest parameterupdated_at - breaking
added the pattern
^((eq|~eq|neq):)?[^:]+$to thequeryrequest parameterAccept - breaking
added the pattern
^((eq|~eq|neq):)?[^:]+$to thequeryrequest parameterAccepted - breaking
added the pattern
^((eq|~eq|neq):)?[^:]+$to thequeryrequest parameterFromPrincipal - breaking
added the pattern
^((eq|~eq|neq):)?[^:]+$to thequeryrequest parameterPrincipal - breaking
added the pattern
^((eq|~eq|neq):)?[^:]+$to thequeryrequest parameterToPrincipal - breaking
added the pattern
^((eq|~eq|neq):)?[^:]+$to thequeryrequest parameterdomain_sid - breaking
added the pattern
^((eq|~eq|neq):)?[^:]+$to thequeryrequest parameterfinding - breaking
added the pattern
^((eq|~eq|neq):)?[^:]+$to thequeryrequest parameterfrom_principal - breaking
added the pattern
^((eq|~eq|neq):)?[^:]+$to thequeryrequest parameterprincipals_hash - breaking
added the pattern
^((eq|~eq|neq):)?[^:]+$to thequeryrequest parameterto_principal - info
for the
queryrequest parameterAcceptedUntil, the format was generalized fromdate-timeto no format - info
for the
queryrequest parameteraccepted_until, the format was generalized fromdate-timeto no format - info
for the
queryrequest parametercreated_at, the format was generalized fromdate-timeto no format - info
for the
queryrequest parameterdeleted_at, the format was generalized fromdate-timeto no format - info
for the
queryrequest parameterid, the type was generalized fromintegertostring - info
for the
queryrequest parameterupdated_at, the format was generalized fromdate-timeto no format
- breaking