Ellipse Gradient for Header

Kaseya VSA Integration Guide

Integrate Kaseya VSA with enterprise systems through its version-dependent REST APIs, scheduled synchronization, supported notifications, and controlled endpoint workflows.

Kaseya VSA integration options at a glance

Kaseya VSA integrations are primarily implemented through its REST API, whose resources, authentication flow, and permissions vary by release, edition, and deployment model. Martini can retrieve and update supported Organizations, Machines, Agents, Machine Groups, Agent Procedures, and Tickets, while orchestrating pagination, incremental synchronization, validation, and downstream writes. VSA alerts and notifications may support selected event-driven scenarios, but a general-purpose webhook for every resource change was not confirmed. Where callbacks are unavailable, Martini can poll the REST API on a schedule with checkpoints and overlap windows. Credentials, session tokens, tenant context, and permissions are managed through secure environment configuration.

Integration pointSupported by Kaseya VSA?Common use casesHow Martini supports it
REST APIsYesRetrieve Organizations, Machines, Agents, Machine Groups, Agent Procedures, and Tickets; query status; and perform supported create, update, or operational actions.Martini can consume documented VSA REST endpoints, map responses, apply business rules, paginate collections, and expose normalized REST APIs to downstream systems.
Webhooks / outbound callbacksLimitedVSA alerts and notifications may support selected event-delivery scenarios, but a general-purpose callback for every resource change was not confirmed.Martini can receive a documented callback or notification when the target release supports one; otherwise it can use scheduled polling and checkpoints.
AuthenticationLimitedVSA deployments may use user or API credentials, authenticated sessions or bearer-style tokens, tenant context, and role-based permissions.Martini stores credentials and tokens in secure environment configuration and sends the target authentication format without assuming OAuth 2.0 or API-key support.
Scheduled synchronizationYesPolling is an important fallback when VSA does not provide a suitable callback, including inventory, ticket, and status synchronization.Martini scheduler-triggered workflows can use update windows, overlap intervals, pagination, checkpoints, and retryable execution.
File / attachment APIsLimitedFiles, scripts, procedure payloads, or Ticket attachments may be available depending on the VSA version and enabled modules.Martini can process documented file or attachment endpoints, but the implementation must validate the target deployment's supported resources and limits.
Bulk / async / batch APIsNot confirmedA generally documented VSA bulk or asynchronous REST API was not confirmed; large collections should use bounded pagination and checkpointing.Martini can process pages incrementally and control concurrency without assuming a dedicated bulk endpoint.
Database / analytics accessNot confirmedDirect access to the VSA production datastore was not confirmed as a supported customer-facing integration method.Martini should consume the VSA API or supported reporting exports rather than depend on direct database access.
SDKsNot confirmedNo specific official VSA SDK was confirmed for this research.Martini can consume documented VSA HTTP APIs directly, so an SDK is not required.

How Kaseya VSA exposes data and business events

Kaseya VSA REST APIs

The REST API is the primary VSA integration mechanism. It can expose Organizations, Machines, Agents, Machine Groups, Agent Procedures, Tickets, endpoint status, and supported operational actions, although exact endpoints and authentication vary by release and deployment.

Martini implementation pattern

Martini implementation pattern: Martini authenticates against the documented VSA endpoint, retrieves resources through a workflow, follows pagination, transforms VSA responses into canonical models, applies business rules, and writes to downstream systems or exposes a normalized Martini API.

Implementation sequence

Confirm the VSA base URL, API version, resources, and tenant context
Store credentials or session-token settings in Martini environment configuration
Authenticate and establish the required VSA session or token
Retrieve the required VSA resource pages
Map VSA objects into the canonical integration model
Apply validation, authorization, and routing rulesして対象 systems

Kaseya VSA notifications and callbacks

VSA provides operational alerts and notifications, but a general-purpose webhook facility covering every object change was not confirmed. Event delivery must be verified for the target release and enabled modules.

Martini implementation pattern

Martini implementation pattern: When a documented callback or supported notification exists, Martini receives it, validates its authenticity and payload, retrieves authoritative VSA data when needed, and routes the result. Unsupported event types use scheduled REST polling instead.

Implementation sequence

Verify the supported VSA notification or callback mechanism
Receive the notification through a Martini API or webhook workflow
Validate the source, payload, and event identifier
Retrieve the current VSA resource when the notification is not authoritative
Deduplicate the event and route it to the target workflow
Record processing status and retry transient failures

Kaseya VSA scheduled synchronization

Scheduled polling is the principal fallback when VSA cannot deliver the required changes through a callback. It is suitable for endpoint inventories, status data, Organizations, and Tickets.

Martini implementation pattern

Martini implementation pattern: A scheduler-triggered workflow queries changed VSA objects using documented filters where available, uses an overlap window for clock skew and delayed indexing, and stores a high-water mark or object checkpoint for safe incremental processing.

Implementation sequence

Start the workflow on a controlled schedule
Load the last successful synchronization checkpoint
Query VSA with an overlapping update window
Follow all documented response pages
Upsert objects using stable VSA identifiers
Persist the checkpoint only after successful processing

Kaseya VSA file and attachment operations

Files, scripts, procedure payloads, or Ticket attachments may be exposed by particular VSA versions and modules, but a general-purpose file API was not confirmed.

Martini implementation pattern

Martini implementation pattern: Martini can process documented file or attachment endpoints as an optional workflow branch, validating content type, size, ownership, and target permissions before transferring or storing content.

Implementation sequence

Confirm that the target VSA version exposes the required file resource
Authenticate with permissions limited to the required content
Retrieve or submit the documented file or attachment payload
Validate size, type, ownership, and association
Transform or route the content to the target system
Record transfer status without exposing sensitive content in logs

Common Kaseya VSA integration patterns

Pattern 1: Synchronize VSA endpoint inventory

When to use this pattern

Use this pattern to maintain a central asset or configuration inventory from VSA Organizations, Machines, Agents, and Machine Groups. It is appropriate for scheduled synchronization when a complete event stream is unavailable.

Integration direction
Kaseya VSA
Martini
ServiceNow
Example Mapping
Kaseya VSA FieldCanonical FieldTarget Field
Organization.idcustomerExternalIdcompany.external_id
Machine.idendpointExternalIdcmdb_ci.u_vsa_id
Machine.nameendpointNamecmdb_ci.name
Agent.statusagentStatuscmdb_ci.u_agent_status
Martini implementation pattern

A scheduler-triggered Martini workflow authenticates to VSA, retrieves paginated resources, joins endpoint ownership, normalizes status values, and upserts target records. It uses an overlap window, stable identifiers, checkpoints, and retry handling for incomplete pages or transient failures.

Martini capabilities used
  • workflows
  • scheduled triggers
  • API consumption
  • pagination orchestration
  • data mapping
  • business rules
  • error handling

Pattern 2: Route VSA alerts and Tickets

When to use this pattern

Use this pattern to route supported VSA notifications or scheduled Ticket and alert queries into a service-management platform while preserving machine and Organization context.

Integration direction
Kaseya VSA
Martini
Jira Service Management
Example Mapping
Kaseya VSA FieldCanonical FieldTarget Field
Ticket.idincidentExternalIdissue.externalId
Ticket.priorityseveritypriority
Machine.idendpointExternalIdcustomfield.vsaMachineId
Organization.namecustomerNamecustomfield.customer
Martini implementation pattern

Martini receives a supported notification or polls changed Tickets, enriches each item with VSA endpoint context, maps priority and status, suppresses duplicates by VSA identifier, and creates or updates the target issue. Retryable API failures are separated from validation and authorization errors.

Martini capabilities used
  • webhook reception
  • scheduled workflows
  • data enrichment
  • mapping
  • deduplication
  • business rules
  • error handling

Pattern 3: Orchestrate an authorized Agent Procedure

When to use this pattern

Use this pattern when an internal application needs to request a controlled VSA Agent Procedure and the target VSA API exposes the required operation.

Integration direction
Internal request API
Martini
Kaseya VSA
Example Mapping
Kaseya VSA FieldCanonical FieldTarget Field
request.organizationIdorganizationExternalIdOrganization.id
request.machineGroupIdtargetGroupExternalIdMachine Group.id
request.procedureNameapprovedProcedureAgent Procedure.name
request.correlationIdoperationCorrelationIdVSA operation reference
Martini implementation pattern

Martini exposes a controlled API, authenticates the caller, validates the Organization or Machine Group scope, checks an allow-list of procedures, and invokes only the documented VSA operation. The workflow records authorization, target scope, correlation data, and outcome, while avoiding uncontrolled retries of endpoint-changing actions.

Martini capabilities used
  • API exposure
  • authentication and authorization
  • workflows
  • validation
  • business rules
  • audit logging
  • controlled error handling

Pattern 4: Publish normalized VSA reporting data

When to use this pattern

Use this pattern when multiple operational applications need consistent VSA customer, endpoint, and ticket data without each application implementing VSA-specific API logic.

Integration direction
Kaseya VSA
Martini
Microsoft Excel
Example Mapping
Kaseya VSA FieldCanonical FieldTarget Field
Organization.namecustomerNameCustomer
Machine.nameendpointNameEndpoint
Machine.operatingSystemoperatingSystemOperating System
Agent.statusconnectivityStatusAgent Status
Martini implementation pattern

Martini periodically retrieves VSA data, applies canonical mappings and reporting rules, generates a controlled export or exposes a normalized REST endpoint, and records source version, checkpoint, and incomplete-page information for operational traceability.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • data mapping
  • JSON handling
  • file processing
  • API exposure
  • monitoring

Applications commonly integrated with Kaseya VSA

Kaseya VSA can be integrated with adjacent service-management, collaboration, remote-support, and reporting products. These patterns should be validated against the target VSA release, enabled modules, and the capabilities of the receiving application.

Application Scenario Direction Martini Pattern
ConnectWise Manage Align managed endpoints, customer Organizations, alerts, and service Tickets with MSP service operations. Kaseya VSA → Martini → ConnectWise Manage Martini retrieves VSA Organizations, Machines, Agents, and Tickets, maps stable identifiers into ConnectWise records, applies ticket-priority rules, and uses idempotent upserts with retry handling.
Datto Autotask PSA Synchronize endpoint alerts, customer accounts, configuration information, and service tickets with PSA workflows. Kaseya VSA → Martini → Datto Autotask PSA A scheduled or notification-driven workflow normalizes VSA endpoint and ticket data, resolves customer mappings, writes Autotask objects, and records checkpoints for safe replay.
ServiceNow Create incidents or configuration records from VSA monitoring data and associate endpoint information with operational workflows. Kaseya VSA → Martini → ServiceNow Martini polls or receives supported VSA notifications, enriches incidents with Organization and Machine context, calls ServiceNow APIs, and optionally sends permitted status updates back to VSA.
Jira Service Management Route VSA incidents or operational alerts to IT service teams and correlate remediation status. Kaseya VSA → Martini → Jira Service Management Martini filters and deduplicates VSA Tickets or alerts, maps severity and machine metadata to Jira fields, and handles Jira-to-VSA actions only where authorized VSA operations are available.
Microsoft Teams Deliver selected VSA alerts or ticket notifications to operations channels for triage and escalation. Kaseya VSA → Martini → Microsoft Teams Martini retrieves eligible VSA alerts or Tickets, applies routing and suppression rules, formats operational messages, and sends them through a supported Teams endpoint.
Slack Send operational alerts and escalation messages to support channels. Kaseya VSA → Martini → Slack A Martini workflow polls VSA or processes a supported notification, enriches the alert with Organization and Machine details, and posts only actionable messages with duplicate protection.
Splashtop Correlate VSA-managed Machines with remote-support workflows where both products are used by an MSP. Kaseya VSA → Martini → Splashtop Martini maps VSA endpoint identifiers and organization ownership into a support workflow, validates permitted targets, and exchanges only the remote-support data exposed by the relevant APIs.
Microsoft Excel Produce periodic endpoint, compliance, or operational reports for business and service teams. Kaseya VSA → Martini → Microsoft Excel A scheduled Martini workflow retrieves paginated VSA data, transforms it into reporting columns, and generates or delivers a controlled export while logging incomplete pages and failed objects.

How to build a Kaseya VSA integration in Martini

Objective

Confirm the target VSA release, base URL, API version, resources, tenant context, and authentication model before building the workflow.

Instructions in Martini

  • Identify the documented VSA REST API for the deployment
  • Confirm whether credentials, session tokens, bearer-style tokens, or tenant context are required
  • Create a least-privilege VSA integration account
  • Store endpoint and credential settings in Martini environment configuration

Objective

Select event delivery only where the VSA deployment documents a suitable callback; otherwise use scheduled polling with an incremental checkpoint.

Instructions in Martini

  • Verify whether the required alert or resource event has a supported callback
  • Use a Martini webhook or API workflow for documented notifications
  • Use a Scheduler Trigger when event coverage is incomplete
  • Define polling frequency and overlap windows

Objective

Retrieve authoritative VSA resources while handling pagination, version differences, and incomplete responses.

Instructions in Martini

  • Call the VSA REST API from a Martini workflow
  • Follow the documented pagination mechanism
  • Retrieve current resource details when notifications contain only summaries
  • Persist page or high-water-mark state for long-running synchronization

Objective

Coordinate the end-to-end workflow from authentication and retrieval through transformation, routing, target writes, and checkpoint persistence.

Instructions in Martini

  • Separate authentication, retrieval, transformation, and target-write stages
  • Use reusable workflow logic for common VSA resource handling
  • Apply bounded concurrency and configurable delays
  • Keep procedure-execution flows separate from read-only synchronization flows

Objective

Translate VSA Organizations, Machines, Agents, Machine Groups, Procedures, and Tickets into canonical and target-specific schemas.

Instructions in Martini

  • Map stable VSA identifiers rather than display names
  • Normalize statuses, priorities, timestamps, and relationships
  • Validate required fields before downstream writes
  • Preserve source identifiers for reconciliation and replay

Objective

Apply customer routing, deduplication, authorization, and endpoint-scope rules before making downstream or endpoint-changing calls.

Instructions in Martini

  • Resolve Organization and Machine ownership
  • Suppress duplicate alerts or Tickets using stable identifiers
  • Allow-list Agent Procedures and restrict target scope
  • Classify retryable failures separately from validation and authorization failures

Common Kaseya VSA data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
OrganizationsRepresent customers or business entities managed in VSA and provide ownership context for endpoint and ticket data.ConnectWise Manage, Datto Autotask PSA, ServiceNow, reporting storesMartini retrieves Organizations, validates identifiers and tenant context, maps customer fields, and performs idempotent upserts.
MachinesRepresent managed endpoints and their operational or inventory attributes.ServiceNow, ConnectWise Manage, Datto Autotask PSA, Excel reportsMartini retrieves paginated or incrementally changed Machines, normalizes status and ownership, and writes stable VSA identifiers to targets.
AgentsRepresent installed endpoint agents, connectivity, status, and associated metadata.Asset inventories, PSA platforms, reporting storesMartini joins Agents with Machines and Organizations, handles missing or stale relationships, and applies target-specific mappings.
Machine GroupsGroup Machines for organization, policy assignment, and procedure targeting.Service desks, asset platforms, operational reportingMartini maps group membership and identifiers, validates target scope, and preserves relationships during synchronization.
Agent ProceduresRepresent automation procedures deployed to Machines or Machine Groups.Internal request APIs, audit stores, service-management platformsMartini can orchestrate permitted procedure operations only when exposed by the target API, using allow-lists, authorization checks, and audit logging.
TicketsTrack service or operational issues where the VSA edition and enabled modules expose ticket functionality.ConnectWise Manage, Datto Autotask PSA, ServiceNow, Jira Service ManagementMartini maps ticket identifiers, priority, status, and endpoint context, suppresses duplicates, and sends updates only where supported.

Authentication and security considerations

Version-dependent authentication

VSA authentication varies by generation, edition, hosting model, and deployment configuration. Confirm whether the target API uses user credentials, API credentials, an authenticated session, a bearer-style token, or tenant-specific context. Do not assume OAuth 2.0 or API-key support.

Least-privilege access

Use a dedicated VSA integration account with permissions limited to the required Organizations, Machines, procedures, Tickets, and administrative operations. Read-only synchronization should not receive procedure-execution privileges.

Secure configuration

  • Store credentials, tokens, endpoint settings, and tenant context in Martini environment configuration or secrets management.
  • Do not embed secrets in mappings or write tokens to workflow logs.
  • Protect endpoint-changing workflows with authorization, allow-listed procedures, scope restrictions, and audit correlation identifiers.

Operational considerations for Kaseya VSA integrations

Pagination and checkpoints

Machine and Ticket collections can be large. Follow the documented pagination model, persist page or high-water-mark state, and commit checkpoints only after successful processing.

Incremental synchronization

Use update-time filters where available with an overlap interval to account for clock skew and delayed indexing. Store the timestamp, object identifier, query parameters, and execution result.

Retries and idempotency

Rate limits were not confirmed, so use conservative concurrency and configurable delays. Retry transient timeouts and server errors with backoff, but do not blindly retry authentication, authorization, invalid-parameter, or endpoint-changing failures.

Schema and version changes

VSA resources and fields vary by release and enabled modules. Validate required fields, isolate VSA-specific mappings, and monitor changes to status values, nested structures, null handling, and identifier formats.

  • Use stable VSA identifiers instead of display names.
  • Prefer idempotent target upserts.
  • Log enough context to replay failed pages safely without exposing credentials.

Why use Martini instead of scripts or point-to-point integrations?

More than a point-to-point script

Martini separates VSA API consumption from transformation, routing, target writes, and operational controls. This makes version-specific mappings and business rules easier to maintain than duplicated scripts or tightly coupled integrations.

Controlled orchestration

Workflows can combine scheduled polling, supported notifications, pagination, checkpoints, validation, enrichment, and downstream API calls while distinguishing retryable failures from business and authorization errors.

Reusable integration assets

Martini can expose normalized APIs and reuse workflow logic for multiple consumers. Teams can centralize authentication, mappings, deduplication, monitoring, and deployment configuration instead of rebuilding VSA-specific behavior in every application.

Frequently asked questions

How can Kaseya VSA be integrated with enterprise systems?

Kaseya VSA is primarily integrated through its version-dependent REST API. Organizations, Machines, Agents, Machine Groups, Agent Procedures, and, where enabled, Tickets can be retrieved or updated through supported operations. Alerts and notifications may support selected event-driven scenarios, while scheduled API polling is the fallback when a suitable callback is unavailable.

Can Martini integrate with Kaseya VSA?

Yes. Martini can consume the Kaseya VSA REST API, orchestrate scheduled synchronization, receive a documented callback or notification when the target release supports one, map VSA objects, and expose normalized REST APIs for downstream applications.

Do I need a connector to integrate Kaseya VSA with Martini?

No. A dedicated Kaseya VSA connector is not required. Martini can integrate using VSA's confirmed native REST API and authentication mechanisms, plus supported notifications, callbacks, or scheduled polling.

Is there any extra Lonti cost to integrate Kaseya VSA with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Kaseya VSA. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Kaseya, hosting providers, cloud infrastructure, or other third-party systems.

Which Kaseya VSA integration method should be used?

Use the VSA REST API as the primary method, after confirming the release-specific endpoints, authentication flow, tenant context, and permissions. Use documented callbacks or notifications for selected event-driven cases, and scheduled polling with checkpoints for changes that cannot be delivered as events.

Does Kaseya VSA support webhooks or event callbacks?

VSA supports operational alerts and notifications, but a general-purpose webhook covering every Organization, Machine, Agent, Procedure, Ticket, or audit change was not confirmed. Verify the target release and modules; otherwise use scheduled REST API polling.

How does Martini synchronize large VSA inventories?

Martini can use documented pagination, incremental filters where available, bounded concurrency, overlap windows, stable VSA identifiers, and persisted checkpoints. Idempotent upserts and duplicate detection allow a failed or repeated synchronization to resume safely.

Can Martini expose an API façade for Kaseya VSA data?

Yes. Martini can expose a REST API that normalizes selected VSA Organizations, Machines, Agents, Machine Groups, or Tickets for downstream consumers. The façade can centralize authentication, mapping, validation, authorization, and VSA version-specific behavior.

Related Martini documentation

APIs

Workflows

Data

Security

Operations

Integrate Kaseya VSA with Martini

Use Martini to connect Kaseya VSA REST APIs, supported notifications, and scheduled synchronization workflows with the systems that manage your service operations, endpoint data, and reporting.

EXPLORE MARTINI
BOOK A DEMO