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 Incident API

Incident operations

Documentation Provider Profile APIs.io OpenAPI GitHub

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

This API exposes 16 operations across 12 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 4178275a824512c2fd3a2acdb0e8277233919054 v2.71.0.

Requests are made against a single base URL, /.

16 operations 12 paths 18 schemas 2 DELETE9 GET1 PATCH3 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
4178275a824512c2fd3a2acdb0e8277233919054 v2.71.0
Base URL
https://private.intel.amp.cisco.com
Authentication
API Key, OAuth 2.0
Contact
Cisco Security Business Group -- Advanced Threat
License
All Rights Reserved
Resource Areas
1

Authentication & Security 2

Cisco XDR Incident API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (JWT). It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 6 scopes. By default, every request must be authenticated.

  • JWT — Ex: Bearer \

Paths & Operations 16

Across 12 paths, the API surfaces 16 operations — 2 DELETE, 9 GET, 1 PATCH, 3 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Incident 16

Incident operations

POST
/ctia/incident/{id}/status
Update an Incident Status
2 params body → 200
POST
/ctia/incident
Adds a new Incident
1 param body → 201
PUT
/ctia/incident/{id}
Update an existing Incident
2 params body → 200
PATCH
/ctia/incident/{id}
Partially update an existing Incident
2 params body → 200
GET
/ctia/incident/{id}
Get one Incident by ID
2 params → 200
DELETE
/ctia/incident/{id}
Delete one Incident
2 params → 204
GET
/ctia/incident/external_id/{external_id}
List Incident by external id
7 params → 200
GET
/ctia/incident/search
Search for Incident entities using a ES query syntax and field filters
27 params → 200
DELETE
/ctia/incident/search
Delete Incident entities matching given Lucene/ES query string or/and field filters
21 params → 200
GET
/ctia/incident/search/count
Count Incident matching a Lucene/ES query string and field filters
19 params → 200
GET
/ctia/incident/metric/average
Average for some Incident field. Use X-Total-Hits header on response for count used for average. For aggregate-on field X.Y.Z, response body will be {:data {:X {:Y {:Z }}}}. If X-Total-Hits is 0, the…
21 params → 200
GET
/ctia/incident/metric/histogram
Histogram for some Incident field
23 params → 200
GET
/ctia/incident/metric/topn
Topn for some Incident field
23 params → 200
GET
/ctia/incident/metric/cardinality
Cardinality for some Incident field
20 params → 200
POST
/ctia/incident/{id}/link
Link an Incident to a Casebook or Investigation
1 param body → 201
GET
/ctia/{observable_type}/{observable_value}/sightings/incidents
Returns Incident references associated with the specified observable based on Sighting relationships
7 params → 200

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are NewIncident (37 properties), PartialNewIncident (37 properties), PartialIncident (37 properties), Incident (30 properties). Each schema is shown below with its type and property counts.

IncidentScores
object
Used to indicate the severity or impact score of the threat represented by the incident.
MetricResultFilters
object
2 properties 2 required
MetaData
object
metadata associated to the incident.
PartialNewIncidentIncidentTime
object
Relevant time values associated with this Incident.
7 properties
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
IncidentTime
object
Relevant time values associated with this Incident.
7 properties 1 required
PartialNewIncidentScores
object
5 properties
PartialNewIncident
object
Incident partial update
37 properties
Incident
object
Information about computer security incident response. A computer security incident is a violation or imminent threat of violation of computer security policie…
30 properties
IncidentStatusUpdate
object
an Incident Status Update
1 property 1 required
IncidentLinkRequest
object
an Incident Link request
3 properties
NewIncidentScores
object
5 properties
PartialNewIncidentExternalReferences
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
MetricResultData
object
Relationship
object
Represents a relationship between two entities.
17 properties
NewIncident
object
a new Incident
37 properties 3 required
MetricResult
object
3 properties 3 required
PartialIncident
object
37 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cisco-xdr-incident-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
#Incident#Security#XDR#Threat Detection
← Back to C APIs
API Details
ID
cisco-xdr:cisco-xdr-incident-api
Base URL
https://private.intel.amp.cisco.com
Docs
https://developer.cisco.com/docs/cisco-xdr/incident-management-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-incident-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/cisco-xdr-incident-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 Incident 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.