Ellipse Gradient for Header

Veeam Data Cloud Integration Guide

Integrate Veeam Data Cloud with enterprise systems through service-specific REST APIs, scheduled workflows, and selected documented event callbacks.

Veeam Data Cloud integration options at a glance

Veeam Data Cloud is a portfolio of tenant-scoped services, so API resources and event coverage depend on the subscribed workload service. Where available, its REST APIs can provide organizations, users, workloads, protection policies, recovery points, and backup activity for operational automation. Some services may expose asynchronous operations or selected callback mechanisms, while generic bulk, file, and attachment APIs are not universal. Authentication is service-specific and may use OAuth 2.0, bearer tokens, or API credentials. Martini can securely consume the applicable API, schedule incremental synchronization, process documented callbacks, monitor long-running operations, transform responses, and expose normalized REST APIs to downstream systems.

Integration pointSupported by Veeam Data Cloud?Common use casesHow Martini supports it
REST APIsLimitedThe applicable Veeam Data Cloud service may expose REST resources for organizations, users, workloads, policies, protection status, backup activity, and supported administrative or recovery operations. Resource coverage varies by service and tenant.Martini can consume the service-specific REST API from workflows, manage authentication configuration, paginate through results, map responses, apply business rules, and expose a normalized REST API.
Webhooks / outbound callbacksLimitedA universal callback framework for all backup, recovery, or workload events was not confirmed. Selected services may document notifications for particular event types.Martini can expose a REST endpoint to receive documented callback payloads and start a workflow; when callbacks are unavailable, a scheduler can poll the applicable Veeam API.
Bulk / asynchronous operationsLimitedBackup and recovery actions are inherently asynchronous, but generic bulk API support was not confirmed. An API may return an operation, task, or session identifier for status monitoring.Martini can submit a supported action, persist its identifier, poll a status resource with bounded retries, and handle successful, failed, and timed-out terminal states.
File / attachment APIsLimitedFile-level restore, export, or download capabilities may exist for particular workload services such as Microsoft 365 or Salesforce, but no universal Veeam Data Cloud file API was confirmed.Martini can process a documented file or attachment response using the applicable transfer format and route it to an approved destination, but the endpoint must be verified for the selected service.
AuthenticationLimitedAuthentication and authorization are service- and tenant-dependent. Applicable services may use OAuth 2.0, bearer tokens, or API credentials with organization, subscription, or workload permissions.Martini can store secrets securely, configure authenticated API calls, separate environment credentials, and implement token renewal or credential rotation according to the service API.
Scheduled synchronizationYesPolling is the fallback when event callbacks are unavailable and is useful for protection inventory, backup sessions, compliance reporting, and status changes.Martini scheduler-triggered workflows can retrieve incremental pages, retain checkpoints, apply bounded concurrency, and publish changes to operational or reporting systems.
Database / analytics accessNoDirect access to Veeam Data Cloud internal operational databases was not confirmed. Reporting should use documented APIs, supported exports, or an external data store.Martini can normalize API results and write them to an external SQL or analytics platform, without assuming access to Veeam-managed databases.

How Veeam Data Cloud exposes data and business events

Veeam Data Cloud REST APIs

REST is the expected primary integration mechanism where the subscribed Veeam Data Cloud service provides API access. Available resources and permissions vary by service and tenant, but may include organizations, users, workloads, protection policies, recovery points, activities, and supported administrative actions.

Martini implementation pattern

Martini authenticates to the applicable Veeam REST API, retrieves resources through a workflow, follows pagination or continuation data, and maps service-specific responses into a canonical operational model. The workflow can then update a target system, write an external reporting store, or expose a normalized Martini API.

Implementation sequence

Confirm the subscribed Veeam Data Cloud service and API base URL
Configure tenant-scoped credentials and permissions in Martini secrets
Call the applicable Veeam REST resource
Follow pagination and retain the synchronization checkpoint
Map the response into the target data model
Apply protection, compliance, or routing rules and write the result

Veeam Data Cloud callbacks

A general-purpose webhook framework for every Veeam Data Cloud event was not confirmed. A selected service may expose callback or event-notification support for particular operational events, so the event catalog and payload contract must be verified before implementation.

Martini implementation pattern

When a documented callback is available, Martini exposes a REST API endpoint that validates the request, records the source event identifier, and starts a workflow. If the selected service has no callback for the required event, Martini uses scheduled polling of sessions, activities, or protection status instead.

Implementation sequence

Verify that the selected Veeam service documents the required callback event
Expose a secured Martini REST endpoint for the callback
Validate authentication, tenant scope, and payload fields
Deduplicate the event using its source identifier or a derived key
Retrieve current Veeam state when the callback is only a notification
Route the normalized event to the target workflow

Veeam Data Cloud asynchronous operations

Backup and recovery activities can run asynchronously, although generic bulk API support was not confirmed. Where an API returns an operation, task, or session identifier, that identifier should be treated as the handle for monitoring the action.

Martini implementation pattern

Martini submits the supported operation, persists the returned identifier, and starts a bounded polling process. The workflow interprets documented terminal states, applies timeout and retry rules, and records the final outcome for audit or downstream notification.

Implementation sequence

Submit the documented backup, recovery, or administrative operation
Persist the returned operation or session identifier
Poll the documented status resource at controlled intervals
Apply transient-error retries and a maximum polling duration
Map the terminal state and diagnostics
Notify or update the target system with the final result

Common Veeam Data Cloud integration patterns

Pattern 1: Send backup failures to ServiceNow

When to use this pattern

Use this pattern when operations teams need incidents for unresolved failed sessions or protection activities. A scheduled workflow is appropriate when the selected Veeam service does not provide a documented callback for the required event.

Integration direction
Veeam Data Cloud
Martini
ServiceNow
Example Mapping
Veeam Data Cloud FieldCanonical FieldTarget Field
session or activity identifierexternalEventIdcorrelation_id
organization identifierorganizationIdaccount or company
workload identifierprotectedWorkloadIdconfiguration item
failure reasonfailureSummarydescription
Martini implementation pattern

A scheduler-triggered Martini workflow retrieves paginated failed sessions, filters unresolved or newly changed activity, and uses the Veeam identifier as an idempotency key. It enriches the incident with workload, organization, failure reason, and last-successful-backup information, then creates or updates ServiceNow. Transient API and target errors are retried, while invalid permissions or malformed requests are routed for operational review.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • pagination and checkpointing
  • data mapping
  • business rules
  • idempotent upserts
  • error handling

Pattern 2: Synchronize protected workloads with a CMDB

When to use this pattern

Use this pattern to maintain an operational inventory of organizations, workloads, policies, and recent protection state in ServiceNow or another CMDB. It is useful for identifying new, removed, unprotected, or recently changed workloads.

Integration direction
Veeam Data Cloud
Martini
ServiceNow
Example Mapping
Veeam Data Cloud FieldCanonical FieldTarget Field
workload identifiersourceWorkloadIdconfiguration item key
workload typeworkloadTypeclass
protection policy identifierpolicyIdprotection policy
last successful protection timelastProtectedAtlast backup time
Martini implementation pattern

Martini retrieves organizations and workload pages, joins policy and recent activity data where the service API permits, and transforms the service-specific model into CMDB fields. Business rules classify new, removed, and unprotected workloads. Upsert keys prevent duplicates, and a checkpoint allows the next run to process only the required scope or time window.

Martini capabilities used
  • scheduled workflows
  • API orchestration
  • data mapping
  • transformation
  • business rules
  • incremental synchronization
  • retry handling

Pattern 3: Publish protection health notifications

When to use this pattern

Use this pattern when engineering or infrastructure teams need concise alerts in Microsoft Teams or Slack for protection failures, compliance exceptions, or recovery outcomes. It can use polling or a documented callback for selected events.

Integration direction
Veeam Data Cloud
Martini
Microsoft Teams or Slack
Example Mapping
Veeam Data Cloud FieldCanonical FieldTarget Field
backup session statusprotectionStatusalert severity
workload identifierprotectedWorkloadIdmessage subject
failure reasonstatusDetailmessage body
end timeobservedAtevent timestamp
Martini implementation pattern

The workflow receives a documented callback or polls the relevant Veeam activity resource, compares the current state with the stored checkpoint, and suppresses unchanged notifications. Martini applies severity and channel-routing rules, formats the message, and calls the target application endpoint. Failed deliveries are retried with bounded backoff and retained for later review.

Martini capabilities used
  • webhook API exposure
  • scheduler triggers
  • state comparison
  • mapping and transformation
  • routing rules
  • retry and duplicate handling

Pattern 4: Build a backup compliance report

When to use this pattern

Use this pattern to create a repeatable reporting dataset for workload coverage, recent successful protection, failed sessions, recovery-point age, and organization-level compliance rules.

Integration direction
Veeam Data Cloud
Martini
Reporting database
Example Mapping
Veeam Data Cloud FieldCanonical FieldTarget Field
organization identifierorganizationIdorganization_key
protected workload identifierworkloadIdworkload_key
last successful protection timelastSuccessAtlast_success_at
session warning or failureprotectionExceptionexception_detail
Martini implementation pattern

A scheduled Martini workflow extracts the available Veeam resources, follows pagination, normalizes service-specific statuses, and evaluates rules such as stale protection, excessive failures, or insufficient coverage. It writes an idempotent reporting dataset to an external database and records extraction checkpoints. Partial failures are isolated by resource or page so a transient problem does not silently invalidate the entire report.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • pagination
  • data normalization
  • business rules
  • database integration
  • checkpointing and error handling

Applications commonly integrated with Veeam Data Cloud

Veeam Data Cloud can be integrated with workload platforms, service-management tools, notification systems, and observability products. The downstream flows below are architecture patterns; exact Veeam API coverage and target-system implementation should be confirmed for the selected service and tenant.

Application Scenario Direction Martini Pattern
Microsoft 365 Veeam Data Cloud protects Microsoft 365 data, while enterprise workflows can report protection status, backup activity, or recovery information to operational systems. Microsoft 365 → Veeam Data Cloud → Martini Use the applicable Veeam service API to retrieve Microsoft 365 workload and protection information, normalize the response, and route status or compliance results to downstream workflows.
Salesforce Veeam Data Cloud provides Salesforce data protection, and enterprises may need protection and recovery status in operational or compliance reporting. Salesforce → Veeam Data Cloud → Martini Poll the service-specific Veeam API for Salesforce workloads, activities, and recovery information, then map stable identifiers and status values into a canonical protection model.
Microsoft Azure Azure workloads can be protected through Veeam Data Cloud services and their protection state can be centralized for operations and governance. Microsoft Azure → Veeam Data Cloud → Martini Schedule a Martini workflow to retrieve Azure workload and policy data from the applicable Veeam API, apply tenant and compliance rules, and publish normalized results.
ServiceNow Backup failures and protection changes can create or update incidents, operational records, or inventory information for enterprise response. Veeam Data Cloud → Martini → ServiceNow Poll Veeam backup sessions or activities, use the Veeam identifier as an idempotency key, upsert ServiceNow incidents or records, and update them when later sessions succeed.
Microsoft Teams Operations teams can receive notifications about backup failures, compliance exceptions, or recovery activity in collaboration channels. Veeam Data Cloud → Martini → Microsoft Teams Use a scheduled Veeam status workflow or a documented callback where available, filter state changes, format a concise message, and call the target Teams endpoint with duplicate suppression.
Slack Engineering and infrastructure teams can receive operational alerts for failed protection sessions or recovery events in Slack channels. Veeam Data Cloud → Martini → Slack Retrieve or receive Veeam status changes, apply severity and routing rules in Martini, and publish only new or materially changed events to the appropriate Slack destination.
Splunk Backup sessions, failures, and protection metrics can be normalized for security, operations, and compliance analysis. Veeam Data Cloud → Martini → Splunk Extract paginated Veeam activity data, transform it into a stable event schema, preserve source identifiers and timestamps, and send the result to the approved Splunk ingestion interface.
Datadog Protection health and backup-failure indicators can be combined with infrastructure monitoring data and operational dashboards. Veeam Data Cloud → Martini → Datadog Collect selected Veeam status values on a schedule, calculate approved health metrics, and publish them through the target monitoring interface with bounded retries and checkpointing.

How to build a Veeam Data Cloud integration in Martini

Objective

Confirm the purchased Veeam Data Cloud service, tenant scope, API base URL, resource permissions, and authentication method before building the workflow.

Instructions in Martini

  • Identify the service-specific API reference and available resources
  • Configure OAuth 2.0, bearer-token, or API credentials as documented by the service
  • Store client secrets, tokens, and credentials in Martini secrets
  • Separate development, test, and production configuration

Objective

Select the event-driven or scheduled entry point that matches the Veeam service capabilities and the required freshness of the integration.

Instructions in Martini

  • Use a documented Veeam callback only for events explicitly supported by the selected service
  • Expose a secured Martini API endpoint when callbacks are available
  • Use a scheduler trigger to poll sessions, activities, workloads, or protection status when callbacks are unavailable
  • Define the polling window and synchronization checkpoint

Objective

Call the applicable Veeam REST resources and retrieve complete, correctly scoped results without assuming a universal Veeam Data Cloud object model.

Instructions in Martini

  • Call the tenant- or organization-scoped resource
  • Follow page, cursor, or continuation information
  • Retrieve related policies, workloads, or activity details when required
  • Persist operation, session, or activity identifiers for later processing

Objective

Coordinate API calls, enrichment, conditional routing, and asynchronous monitoring in a maintainable Martini workflow.

Instructions in Martini

  • Separate extraction, normalization, business rules, and target delivery into clear workflow stages
  • Treat long-running actions as submit-and-monitor processes
  • Bound concurrency and polling duration
  • Route permanent failures and unsupported operations to an operational error path

Objective

Convert service-specific Veeam responses into a stable canonical model before writing to downstream applications or databases.

Instructions in Martini

  • Map organizations, workloads, policies, recovery points, and sessions to explicit canonical fields
  • Normalize timestamps, status values, identifiers, and warning or error details
  • Preserve source identifiers and request diagnostics
  • Handle optional properties and workload-specific response structures

Objective

Implement protection, compliance, routing, and idempotency rules that determine whether a result creates, updates, alerts, or is ignored.

Instructions in Martini

  • Use stable Veeam identifiers as external keys
  • Filter unresolved failures or changed status values
  • Apply stale-protection, coverage, severity, and retention rules where required
  • Avoid duplicate incidents, messages, and report rows

Common Veeam Data Cloud data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
OrganizationsRepresent customer or tenant organizations managed in the Veeam Data Cloud environment and provide scope for inventory, permissions, and reporting.ServiceNow, reporting databases, Splunk, DatadogMartini retrieves organizations from the service-specific API, preserves tenant and organization identifiers, maps organizational attributes to a canonical model, and upserts the target record.
UsersRepresent administrative or operational users associated with an organization and support ownership, access, or audit reporting.ServiceNow, identity reporting, compliance databasesMartini reads only the fields permitted by the API, applies privacy and access rules, and synchronizes changes using stable user identifiers.
WorkloadsRepresent protected data sources such as Microsoft 365 users, Salesforce data, or Azure resources.ServiceNow CMDB, reporting databases, Splunk, DatadogMartini retrieves workload inventory with pagination and incremental filters where available, maps workload type and protection state, and distinguishes new, removed, and unprotected workloads.
Backup jobs or protection policiesDefine what is protected and how protection is performed for an applicable service or workload group.ServiceNow, compliance reporting, configuration repositoriesMartini normalizes service-specific policy fields, compares policy changes, applies coverage rules, and records the source identifier and effective status.
Recovery pointsRepresent available protected versions or restore points for a workload and support retention or recoverability reporting.Compliance databases, reporting platforms, operational dashboardsMartini retrieves recovery-point data where the selected service exposes it, evaluates age and availability rules, and writes normalized results without assuming a universal resource shape.
Backup sessions or activitiesRecord execution status, start and end times, warnings, errors, and operational outcomes for protection activity.ServiceNow, Microsoft Teams, Slack, Splunk, DatadogMartini uses the session or activity identifier for idempotency, filters unresolved failures, creates or updates downstream alerts, and closes or updates them after a later successful session.

Authentication and security considerations

Service-specific authentication

Veeam Data Cloud authentication and authorization depend on the subscribed service and tenant. Confirm the applicable OAuth 2.0 grant, token endpoint, bearer-token model, or API credential requirements in the service API reference.

Tenant and workload permissions

Scope access to the required tenant, organization, subscription, and protected workloads. Use least-privilege permissions for status retrieval, reporting, or administrative actions.

Credential protection

Store client secrets, access tokens, and API credentials in Martini secrets rather than embedding them in workflows. Separate development, test, and production credentials and plan for rotation and token expiration.

Data protection

Protection metadata may contain organization names, workload identifiers, user information, and operational details. Restrict access to Martini APIs and logs, and avoid logging credentials, restore content, or unnecessary personal data.

Operational considerations for Veeam Data Cloud integrations

Service and schema variation

Veeam Data Cloud is a portfolio rather than a single universal API. Confirm the licensed service, region, resource names, permissions, status values, optional fields, and API version before implementation.

Pagination and incremental retrieval

List resources may be paginated. Preserve cursors, continuation tokens, or page numbers, and use timestamps, activity identifiers, or other change markers where available instead of repeatedly retrieving the full inventory.

Throttling and retries

Limits may vary by service and tenant. Bound concurrency, honor Retry-After headers where provided, use exponential backoff for transient failures, and avoid retrying invalid credentials, missing permissions, or malformed requests.

Idempotency and asynchronous work

Use stable Veeam identifiers for incident creation, inventory updates, and status publishing. For long-running actions, persist the operation or session identifier, poll documented status resources, and enforce a maximum duration.

Testing and monitoring

Test tenant scope, pagination, status transitions, optional properties, callback authentication, and target-system failures. Monitor workflow logs, synchronization checkpoints, retry counts, and unresolved sessions, while preserving Veeam request identifiers for diagnostics.

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

Reusable orchestration

Martini separates Veeam API consumption, normalization, business rules, target delivery, and error handling into maintainable workflows rather than duplicating logic across scripts.

Reliable synchronization

Scheduled triggers, checkpoints, pagination handling, idempotent upserts, bounded retries, and asynchronous status monitoring support dependable protection reporting and operational automation.

Controlled API exposure

Martini can expose a normalized REST API so downstream applications do not need to understand service-specific Veeam Data Cloud resources or authentication details.

Adaptable transformations

Mappings and reusable integration assets can accommodate workload-specific schemas, optional fields, status changes, and different target models without creating separate point-to-point implementations for every destination.

Frequently asked questions

How can Veeam Data Cloud be integrated with enterprise systems?

Veeam Data Cloud can be integrated through the service-specific REST APIs available for the subscribed workload service. Organizations, users, workloads, policies, recovery points, and backup activities may be retrieved for reporting, alerting, inventory, and automation. Selected services may also provide event callbacks or asynchronous operation resources, while scheduled API polling is the fallback when callbacks are unavailable.

Can Martini integrate with Veeam Data Cloud?

Yes. Martini can consume the applicable Veeam Data Cloud REST API, store tenant credentials securely, run scheduled synchronization workflows, monitor asynchronous operations, map service-specific responses, and expose normalized REST APIs. If the selected service documents callbacks, Martini can receive them through an API endpoint; exact coverage depends on the service and tenant.

Do I need a connector to integrate Veeam Data Cloud with Martini?

No. A dedicated Veeam Data Cloud connector is not required. Martini can use Veeam's confirmed native integration mechanisms, primarily the applicable REST API and any documented service-specific callbacks, authentication methods, or file endpoints.

Is there any extra Lonti cost to integrate Veeam Data Cloud with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Veeam Data Cloud. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Veeam, cloud infrastructure, or other third-party systems depending on subscription, usage, and deployment model.

Which Veeam Data Cloud integration methods should be used?

REST APIs are the primary expected method where the subscribed Veeam Data Cloud service provides API access. Use documented callback mechanisms only for the events and services they cover, and use scheduler-triggered polling for protection status or activity when callbacks are unavailable. Generic GraphQL and SOAP support was not confirmed, and direct database access should not be assumed.

Does Veeam Data Cloud provide webhooks or callbacks for backup events?

A universal webhook framework for every backup, recovery, or workload event was not confirmed. A selected service may support callback-style notifications for particular events. The event catalog, authentication requirements, and payload contract must be verified; otherwise Martini can poll the relevant sessions, activities, or protection resources.

How does Martini synchronize Veeam Data Cloud data?

Martini can run scheduled workflows that retrieve paginated organizations, workloads, policies, recovery points, or backup activities, then write normalized results to target systems. Where timestamps, activity identifiers, cursors, or change filters are available, the workflow can use incremental checkpoints. Stable Veeam identifiers support idempotent upserts and duplicate prevention.

How are errors, retries, and long-running operations handled?

Martini can distinguish transient throttling, timeouts, and temporary service failures from permanent authentication, permission, or validation errors. Workflows can use bounded retries and backoff, preserve request diagnostics, and route failed items for review. When Veeam returns an operation, task, or session identifier, Martini can poll its status until success, failure, or timeout. Martini can also expose a normalized API façade for downstream applications.

Related Martini documentation

API Integration

Workflows

Security

Operations

Integrate Veeam Data Cloud with Martini

Use Martini to build maintainable Veeam Data Cloud integrations for protection monitoring, workload inventory, compliance reporting, and operational automation.

EXPLORE MARTINI
BOOK A DEMO