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 Target Record API

Target Record operations

Cisco XDR Target Record 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 Target Record, 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 10 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 10 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
License
All Rights Reserved
Resource Areas
1

Authentication & Security 2

Cisco XDR Target Record 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.

Target Record 11

Target Record operations

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

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are PartialTargetRecord (22 properties), NewTargetRecord (22 properties), TargetRecord (15 properties), Target (7 properties). Each schema is shown below with its type and property counts.

MetricResultFilters
object
2 properties 2 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
ObservedTime
object
Period of time when a cyber observation is valid. starttime must come before endtime (if specified).
2 properties 1 required
TargetRecord
object
A TargetRecord is a Sighting that has no threat or observables associated with it, it's a way of saying they saw a set of observables together as a Target.
15 properties
Observable
object
An AssetMapping is a record that a specific Observable maps to an Asset for an indicated period of time.
2 properties 2 required
Target
object
Schema for TargetRecord Targets
7 properties 3 required
MetricResultData
object
MetricResult
object
3 properties 3 required
NewTargetRecord
object
a new Target-record
22 properties 2 required
PartialTargetRecord
object
A TargetRecord is a Sighting that has no threat or observables associated with it, it's a way of saying they saw a set of observables together as a Target.
22 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cisco-xdr-target-record-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 Target Record 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.