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

The Schedules API from Cisco XDR — 2 operation(s) for schedules.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

This API exposes 5 operations across 2 paths, and defines 5 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 5 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 Schedules 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.

Schedules 5
GET
/v1/schedules
Handler to get all schedules.
listSchedules → 200400403404500
POST
/v1/schedules
Handler to creates a schedule.
scheduleCreateRequest body → 201400403404409500
GET
/v1/schedules/{schedule_id}
Handler to get a specific schedule.
getScheduleById 1 param → 200400403404500
PUT
/v1/schedules/{schedule_id}
Handler to updates a schedule. Allows partial update.
scheduleUpdateRequest 1 param body → 200400403404409500
DELETE
/v1/schedules/{schedule_id}
Handler to delete a schedule.
deleteScheduleById 1 param → 204400403404412500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are ScheduleGetResponse (13 properties), ScheduleGetAllResponse (13 properties), ScheduleProperties (8 properties), ScheduleDefinitionPostRequest (5 properties). Each schema is shown below with its type and property counts.

ScheduleGetAllResponse
object
13 properties
ScheduleDefinitionPostRequest
object
Either ViewSchemaID or Type or both can be provided to create a Schedule.
5 properties 1 required
SchedulePutRequest
object
2 properties
ScheduleGetResponse
object
13 properties
ScheduleProperties
object
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cisco-xdr-schedules-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
#Schedules
← Back to C APIs
API Details
ID
cisco-xdr:cisco-xdr-schedules-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-schedules-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/cisco-xdr-schedules-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 Schedules 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.