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

The Triggers API from Cisco XDR — 2 operation(s) for triggers.

Cisco XDR Triggers 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 Triggers. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 2 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://automate.us.security.cisco.com/{basePath}.

5 operations 2 paths 7 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

Cisco XDR Triggers API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oAuth2) using the clientCredentials flow, exposing 26 scopes. By default, every request must be authenticated.

Paths & Operations 5

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

Triggers 5
GET
/v1/workflows/{workflow_id}/triggers
Handler to get all triggers information
getTriggersById 1 param → 200400403404500
POST
/v1/workflows/{workflow_id}/triggers
Handler to get create a trigger for a workflow
triggerCreateRequest 1 param body → 201400403404409500
GET
/v1/workflows/{workflow_id}/triggers/{trigger_id}
Handler to get a trigger information by ID
getTriggerById 2 params → 200400403404500
PUT
/v1/workflows/{workflow_id}/triggers/{trigger_id}
Handler to update trigger
triggerUpdateRequest 2 params body → 200400403404409500
DELETE
/v1/workflows/{workflow_id}/triggers/{trigger_id}
Handler to delete trigger
triggerDeleteRequest 2 params → 204400403404500

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Trigger (17 properties), TriggerPostRequest (7 properties), TriggerPutRequest (6 properties), TriggerStatus (4 properties). Each schema is shown below with its type and property counts.

TriggerStatus
object
4 properties
TriggerPutRequest
object
TriggerPutRequest struct for triggers post api
6 properties 1 required
TriggerType
string
Trigger
object
17 properties
State
string
DefinitionState
StatusDetails
object
3 properties
TriggerPostRequest
object
TriggerPostRequest struct for triggers post api
7 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cisco-xdr-triggers-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 Triggers 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.