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

Kaseya /v2/device API

Operations on devices

Kaseya /v2/device API is one of 488 APIs that Kaseya publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and rate-limit docs.

This API exposes 10 operations across 10 paths, and defines 46 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0 (Build 235_0add0e4d537431f30405d568ccb46b6d7af1f183).

Requests are made against a single base URL, https://syrah-api.centrastage.net/api.

10 operations 10 paths 46 schemas 6 GET2 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0 (Build 235_0add0e4d537431f30405d568ccb46b6d7af1f183)
Base URL
https://api.bms.kaseya.com
Resource Areas
1

Paths & Operations 10

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

/v2/device 10

Operations on devices

PUT
/v2/device/{deviceUid}/site/{siteUid}
Moves a device from one site to another site.
moveDevice 2 params → 500409404403401200
PUT
/v2/device/{deviceUid}/quickjob
Creates a quick job on the device identified by the given device Uid.
createQuickJob 1 param body → 500409404403400401200
POST
/v2/device/{deviceUid}/warranty
Sets the warranty of a device identified by the given device Uid.
setWarrantyData 1 param body → 500409404403400401200
POST
/v2/device/{deviceUid}/udf
Sets the user defined fields of a device identified by the given device Uid.
setUdfFields_1 1 param body → 500409404403400401200
GET
/v2/device/{deviceUid}
Fetches data of the device identified by the given device Uid.
getByUid_1 1 param → 500409404403401200
GET
/v2/device/{deviceUid}/patches
Fetches the patches of the device identified by the given device Uid.
getDevicePatches 4 params → 500409404403400401200
GET
/v2/device/{deviceUid}/alerts/resolved
Fetches the resolved alerts of the device identified by the given device Uid.
getDeviceResolvedAlerts 4 params → 500409404403401200
GET
/v2/device/{deviceUid}/alerts/open
Fetches the open alerts of the device identified by the given device Uid.
getDeviceOpenAlerts 4 params → 500409404403401200
GET
/v2/device/macAddress/{macAddress}
Fetches data of the device(s) identified by the given MAC address in format: XXXXXXXXXXXX
getByMacAddress_1 1 param → 500409200404403401
GET
/v2/device/id/{deviceId}
Fetches data of the device identified by the given device Id.
getById_1 1 param → 500409404403401200

Schemas 46

The contract defines 46 schemas that model the data the API accepts and returns. The most detailed are Udf (300 properties), Device (34 properties), Alert (14 properties), Patch (13 properties). Each schema is shown below with its type and property counts.

WindowsPerformanceContext
TemperatureContext
CreateQuickJobRequest
object
2 properties 2 required
EndpointSecurityThreatContext
JobComponent
object
Job component data
3 properties
ResponseAction
object
5 properties
Patch
object
Patch data for a device
13 properties
FileSystemContext
StatusContext
ActionContext
DiskUsageContext
EndpointSecurityWindowsDefenderContext
WmiContext
SecCenterContext
PatchManagement
object
Patch management data
4 properties
ScriptContext
ErrorResponse
object
Default error response body
4 properties
AlertMonitorInfo
object
Alert monitor information
2 properties
Job
object
Job data
5 properties
RansomWareContext
Antivirus
object
Device antivirus data
2 properties
SNMPProbeContext
AlertContext
object
1 property 1 required
Alert
object
Alert data
14 properties
PsuContext
NetworkMonitorContext
FanContext
PingContext
Udf
object
User defined fields
300 properties
PatchContext
ResourceUsageContext
AlertSourceInfo
object
Alert source information data
4 properties
SecurityManagementContext
JobComponentVariable
object
Job component variable data
2 properties
Device
object
Device data
34 properties
DiskHealthContext
OnlineOfflineStatusContext
PaginationData
object
Pagination data
4 properties
JobComponentRequest
object
Job component request data
2 properties
CustomSNMPContext
EventLogContext
AntivirusContext
BackupManagementContext
DevicesType
object
Devices Type
2 properties
Warranty
object
Device's warranty data
1 property
PrinterContext

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kaseya-v2-device-api-openapi.yml Raw ↑

Other APIs Kaseya publishes across the network.

IT Glue API
Kaseya VSA 9 REST API
Kaseya VSA 10 API
myITprocess API
Kaseya Account Codes API
Kaseya Account Invoice Settings API
Kaseya Accounts API
Kaseya Account Types API
Kaseya Action Types API
Kaseya Additional Invoice Field Values API
Kaseya Admin API
Kaseya Agent Procedure API
Where this information came from

This is an independent, third-party profile of Kaseya /v2/device 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.