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

Events operations

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

This API exposes 9 operations across 7 paths, and defines 42 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: /, https://visibility.amp.cisco.com/.

9 operations 7 paths 42 schemas 2 DELETE6 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 4

Cisco XDR Event API declares 4 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. An API key is passed in the header as authorization (iroh). An API key is passed in the header as authorization (AuthorizationHeader).

  • JWT — Ex: Bearer \
  • AuthorizationHeader — Ex: Bearer \

Paths & Operations 9

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

Event 9

Events operations

GET
/ctia/event/history/{entity_id}
Timeline history of an entity
1 param → 200
GET
/ctia/event/search
Search for Event entities using a ES query syntax and field filters
14 params → 200
DELETE
/ctia/event/search
Delete Event entities matching given Lucene/ES query string or/and field filters
11 params → 200
GET
/ctia/event/search/count
Count Event matching a Lucene/ES query string and field filters
9 params → 200
GET
/ctia/event/{id}
Get one Event by ID
2 params → 200
DELETE
/ctia/event/{id}
Delete one Event
2 params → 204
GET
/iroh/iroh-event/event/{id}
Get an Event
1 param → 200
POST
/iroh/iroh-event/event/search
Search for Events
6 params body → 200
GET
/iroh/iroh-event/event/incident/{incident-id}
Combines events from Private Intel and IROH using the IROH event format
8 params → 200

Schemas 42

The contract defines 42 schemas that model the data the API accepts and returns. The most detailed are Incident (33 properties), User (21 properties), EventDataAdditionalNote (18 properties), AutomationData (13 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.
Response116834EventsFieldsChange
object
2 properties
EventSign
object
3 properties 3 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
GenericSearch
object
EventDataAdditionalNote
object
18 properties 6 required
HighImpactIncidentEventData
object
2 properties 2 required
PrivateIntelIncidentData
object
4 properties 2 required
SearchEventsResult
object
2 properties 2 required
EventEmiter
object
3 properties 2 required
EventDataAdditionalNoteExternalReferences
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
MetaData
object
metadata associated to the incident.
AutomationData
object
13 properties 10 required
IncidentStatusChangeEventData
object
5 properties 5 required
User
object
21 properties 6 required
IdPMapping
object
5 properties 2 required
NotificationRequestEventData
object
2 properties 2 required
IncidentTime
object
Relevant time values associated with this Incident.
7 properties 1 required
EventDataMetadata
object
2 properties
ModuleInstanceEventData
object
5 properties 4 required
PIAMEntitlementData
object
2 properties 2 required
Event
object
7 properties 3 required
SCIMInfos
object
3 properties 3 required
PartialEvent
object
9 properties
SearchEventsResultPaging
object
4 properties 1 required
Cursor
object
3 properties 1 required
Incident
object
33 properties 6 required
UserEventData
object
4 properties 4 required
IncidentEnrichmentEventData
object
2 properties 2 required
PIAMProvisioningEventData
object
13 properties 11 required
EventDataAdditional
object
1 property 1 required
PrivateIntelNoteEventData
object
5 properties 4 required
Response116834EventsEntity
object
IncidentLastActivityChangeEventData
object
3 properties 3 required
EventDataAdditionalNoteRelatedEntities
object
2 properties 2 required
OrgData
object
3 properties 3 required
EventDataRelatedEntities
object
2 properties 2 required
EventDataUpdatedFieldsValue
object
2 properties
UpdatedField
object
3 properties 3 required
EntitlementData
object
2 properties 2 required
EventBucket
object
5 properties 5 required
Update
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cisco-xdr-event-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 Feed API
Where this information came from

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