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

Demisto Entry API

The Entry API from Demisto — 8 operation(s) for entry.

Demisto Entry API is one of 24 APIs that Demisto publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Entry. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 8 operations across 8 paths, and defines 27 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://hostname:443.

8 operations 8 paths 27 schemas 2 GET6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://xsoar.pan.dev
Authentication
API Key, API Key, API Key
Resource Areas
1

Authentication & Security 3

Demisto Entry API declares 3 security schemes for authenticating requests. An API key is passed in the header as Authorization (api_key). An API key is passed in the header as X-XSRF-TOKEN (csrf_token). An API key is passed in the header as x-xdr-auth-id (x-xdr-auth-id). By default, every request must be authenticated.

Paths & Operations 8

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

Entry 8
POST
/entry
Create new entry in existing investigation
investigationAddEntryHandler body → 200412
GET
/entry/artifact/{id}
Get entry artifact
getEntryArtifact 1 param → 200
GET
/entry/download/{entryid}
Download file
downloadFile 1 param → 200
POST
/entry/execute/sync
Create new entry in existing investigation
investigationAddEntriesSync body → 200412
POST
/entry/exportArtifact
Export Artifact
entryExportArtifact body → 200
POST
/entry/formatted
Create new formatted entry in existing investigation
investigationAddFormattedEntryHandler body → 200
POST
/entry/note
Mark entry as note
updateEntryNote body → 200
POST
/entry/tags
Set entry tags
updateEntryTagsOp body → 200

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are Entry (48 properties), FileMetadata (9 properties), HumanCron (7 properties), updateEntry (6 properties). Each schema is shown below with its type and property counts.

updateEntryTags
object
4 properties
EndingType
string
EndingType holds the type of schedule Ending
TermLocationMap
object
ArgAtomicFilter
object
ArgAtomicFilter - operator with two sides that return true/false
5 properties
ComplexArg
object
ComplexArg - all info that is necessary to compute argument value from context Root - the root slice (or object) from to work against Filters - a slice of filt…
4 properties
HumanCron
object
7 properties
Entry
object
Entry holds a single entry in an investigation. Entries entered within a short amount of time by the same user are combined
48 properties
EntryTask
object
EntryTask holds information regarding the related task
4 properties
EntryCategory
string
EntryHistory
object
4 properties
DownloadEntry
object
2 properties
ReputationData
object
ReputationData holds the reputation data (reputation, regex, highlights result)
4 properties
ArrayPositions
array
TransformerOperatorID
string
FileMetadata
object
9 properties
ArgFilter
array
ArgFilter - represent a slice of atomic filters with OR condition between them (e.i. - atomic1 OR atomic2 OR ...)
uploadedEntry
object
3 properties
OperatorArgument
object
2 properties
EntryReputation
object
EntryReputation holds the entry reputations and the highlights
2 properties
FilterOperatorID
string
ArgTransformer
object
2 properties
EntryType
number
EntryType specifies the type of the entry
Locations
array
updateEntry
object
6 properties
AdvanceArg
object
Simple: plain text such as "hello" (constant) or ${File.ID} (DT expression) Complex: struct with all info that is necessary to compute argument value from cont…
2 properties
Location
object
4 properties
FieldTermLocationMap
object

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

demisto-entry-api-openapi.yml Raw ↑

Other APIs Demisto publishes across the network.

Demisto Automation API
Demisto Classifier API
Demisto Contentpacks API
Demisto Dashboards API
Demisto Evidence API
Demisto Incident API
Demisto Incidentfields API
Demisto Incidents API
Demisto Incidenttype API
Demisto Indicator API
Demisto Indicators API
Demisto Inv Playbook API
Where this information came from

This is an independent, third-party profile of Demisto Entry 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.