How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Cisco XDR Inspect API

Inspect related routes

Cisco XDR Inspect API is one of 83 APIs that Cisco XDR publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Inspect, Security, XDR, and Threat Detection. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 1 operation across 1 path, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.107.

Requests are made against a single base URL, https://visibility.amp.cisco.com/.

1 operations 1 paths 6 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.107
Base URL
https://visibility.amp.cisco.com
Authentication
API Key, API Key, OAuth 2.0
Resource Areas
1

Authentication & Security 3

Cisco XDR Inspect API declares 3 security schemes for authenticating requests. An API key is passed in the header as authorization (iroh). An API key is passed in the header as authorization (AuthorizationHeader). It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 25 scopes. By default, every request must be authenticated.

  • AuthorizationHeader — Ex: Bearer \

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Inspect 1

Inspect related routes

POST
/iroh/iroh-inspect/inspect
Find Observables
findObservables body → 200400401403500

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are 403 (8 properties), 401 (6 properties), 500 (3 properties), Observable (2 properties). Each schema is shown below with its type and property counts.

400
object
An object containing the offending parameters.
1 property 1 required
StrContent
object
1 property 1 required
Observable
object
A simple, atomic value which has a consistent identity, and is stable enough to be attributed an intent or nature. This is the classic 'indicator' which might…
2 properties 2 required
401
object
An object describing the problem.
6 properties 1 required
500
object
The error string.
3 properties 1 required
403
object
An object describing the problem.
8 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cisco-xdr-inspect-api-openapi.yml Raw ↑

Other APIs Cisco XDR publishes across the network.

Cisco XDR Actor API
Cisco XDR Asset API
Cisco XDR Asset Mapping API
Cisco XDR Asset Properties API
Cisco XDR Attack Pattern API
Cisco XDR Bulk API
Cisco XDR Bundle API
Cisco XDR Campaign API
Cisco XDR Casebook API
Cisco XDR COA API
Cisco XDR Deliberate API
Cisco XDR Event API
Where this information came from

This is an independent, third-party profile of Cisco XDR Inspect API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.