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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Cisco XDR

Cisco XDR Response API

IROH Response

Documentation Provider Profile APIs.io OpenAPI GitHub

Cisco XDR Response 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 Response, Security, XDR, and Threat Detection. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 3 operations across 3 paths, and defines 29 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/.

3 operations 3 paths 29 schemas 3 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
Contact
Cisco Security Business Group -- Advanced Threat
License
All Rights Reserved
Resource Areas
1

Authentication & Security 3

Cisco XDR Response 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 3

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

Response 3

IROH Response

POST
/iroh/iroh-response/respond/observables
List available actions for an observable
1 param body → 200
POST
/iroh/iroh-response/respond/sighting
List available actions for a sighting
1 param body → 200
POST
/iroh/iroh-response/respond/trigger/{module-instance-id}/{action-id}
Trigger an Action
4 params → 200

Schemas 29

The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are Sighting (33 properties), NetflowType (22 properties), ProcessCreateType (19 properties), Context (12 properties). Each schema is shown below with its type and property counts.

NetflowType
object
22 properties 5 required
ExternalReference
object
External references are used to describe pointers to information represented outside of CTIM. For example, a Malware object could use an external reference to…
5 properties 1 required
ActionResult
object
1 property 1 required
RegistryRenameType
object
8 properties 6 required
HTTPType
object
12 properties 6 required
Context
object
Context including the event type that best fits the type of the sighting.
12 properties
ErrorMessage
object
7 properties 5 required
RegistryDeleteType
object
8 properties 5 required
EnvelopedActions
object
2 properties
ColumnDefinition
object
5 properties 2 required
RegistrySetType
object
10 properties 6 required
FileDeleteType
object
9 properties 6 required
FileCreateType
object
9 properties 6 required
Traffic
object
9 properties 6 required
ObservedTime
object
Period of time when a cyber observation is valid. starttime must come before endtime (if specified).
2 properties 1 required
Sighting
object
A Sighting
33 properties 6 required
FileModifyType
object
9 properties 6 required
FileMoveType
object
10 properties 8 required
ProcessCreateType
object
19 properties 4 required
RegistryCreateType
object
7 properties 5 required
SightingRelationsRelationInfo
object
SightingDataTable
object
An embedded data table for the Sighting.
3 properties 2 required
SensorCoordinates
object
Describes the device that made the sighting (sensor) and contains identifying observables for the sensor.
3 properties 2 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
EnvelopedActionResult
object
2 properties
LibraryLoadType
object
8 properties 6 required
Action
object
9 properties 7 required
ObservedRelation
object
A relation inside a Sighting.
6 properties 4 required
IdentitySpecification
object
Describes the target of the sighting and contains identifying observables for the target.
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Cisco XDR publishes across the network.

Cisco XDR Actor API
AE Profile APIs.io
Cisco XDR Asset API
AE Profile APIs.io
Cisco XDR Asset Mapping API
AE Profile APIs.io
Cisco XDR Asset Properties API
AE Profile APIs.io
Cisco XDR Attack Pattern API
AE Profile APIs.io
Cisco XDR Bulk API
AE Profile APIs.io
Cisco XDR Bundle API
AE Profile APIs.io
Cisco XDR Campaign API
AE Profile APIs.io
Cisco XDR Casebook API
AE Profile APIs.io
Cisco XDR COA API
AE Profile APIs.io
Cisco XDR Deliberate API
AE Profile APIs.io
Cisco XDR Event API
AE Profile APIs.io
#Response#Security#XDR#Threat Detection
← Back to C APIs
API Details
ID
cisco-xdr:cisco-xdr-response-api
Base URL
https://visibility.amp.cisco.com
Docs
https://developer.cisco.com/docs/cisco-xdr/response-api-guide/
Provider
Cisco XDR
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=cisco-xdr-response-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/cisco-xdr-response-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Cisco XDR Response 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.