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

The Investigation API from Cisco XDR — 8 operation(s) for investigation.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

This API exposes 11 operations across 8 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, /.

11 operations 8 paths 18 schemas 2 DELETE7 GET1 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 Investigation 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 11

Across 8 paths, the API surfaces 11 operations — 2 DELETE, 7 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Investigation 11
POST
/ctia/investigation
Adds a new Investigation
1 param body → 201
PUT
/ctia/investigation/{id}
Update an existing Investigation
2 params body → 200
GET
/ctia/investigation/{id}
Get one Investigation by ID
2 params → 200
DELETE
/ctia/investigation/{id}
Delete one Investigation
2 params → 204
GET
/ctia/investigation/external_id/{external_id}
List Investigation by external id
7 params → 200
GET
/ctia/investigation/search
Search for Investigation entities using a ES query syntax and field filters
16 params → 200
DELETE
/ctia/investigation/search
Delete Investigation entities matching given Lucene/ES query string or/and field filters
12 params → 200
GET
/ctia/investigation/search/count
Count Investigation matching a Lucene/ES query string and field filters
10 params → 200
GET
/ctia/investigation/metric/histogram
Histogram for some Investigation field
14 params → 200
GET
/ctia/investigation/metric/topn
Topn for some Investigation field
14 params → 200
GET
/ctia/investigation/metric/cardinality
Cardinality for some Investigation field
11 params → 200

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are NewInvestigation (25 properties), Investigation (25 properties), PartialInvestigation (25 properties), InvestigationExternalReferences (5 properties). Each schema is shown below with its type and property counts.

MetricResultFilters
object
2 properties 2 required
InvestigationTargets
object
Describes the target of the sighting and contains identifying observables for the target.
4 properties 3 required
InvestigationExternalReferences
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
NewInvestigationTargets
object
Describes the target of the sighting and contains identifying observables for the target.
4 properties 3 required
Response116703Targets
object
Describes the target of the sighting and contains identifying observables for the target.
4 properties
Response116703TargetsObservables
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
InvestigationTargetsObservedTime
object
Period of time when a cyber observation is valid. starttime must come before endtime (if specified).
2 properties 1 required
Response116703ExternalReferences
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
NewInvestigation
object
a new Investigation
25 properties 1 required
NewInvestigationTargetsObservedTime
object
Period of time when a cyber observation is valid. starttime must come before endtime (if specified).
2 properties 1 required
MetricResultData
object
Investigation
object
Schema for an Investigation (a work in progress)
25 properties 3 required
PartialInvestigation
object
Schema for an Investigation (a work in progress)
25 properties
MetricResult
object
3 properties 3 required
NewInvestigationExternalReferences
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
InvestigationTargetsObservables
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
NewInvestigationTargetsObservables
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
Response116703TargetsObservedTime
object
Period of time when a cyber observation is valid. starttime must come before endtime (if specified).
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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