Large language models and AI agents can already make decisions, coordinate tasks, and trigger downstream processes. But they haven't been especially skilled at data movement.
API 2.0 gives those systems a direct way to drive CData Sync. With a modern, workspace-aware REST API, Sync can now be controlled programmatically by applications, automation frameworks, and AI-driven workflows. Data pipelines become something software initiates, monitors, and responds to, rather than something managed through static schedules or manual steps.
CData Sync has long been trusted to move data reliably. API 2.0 extends that reliability into AI- and system-driven environments, turning Sync into a controllable component inside modern data platforms instead of a UI-bound tool.
From schedules to system-driven execution
Static schedules solve only part of the problem. Many data workflows are driven by upstream events, downstream dependencies, or decisions made by other systems.
API 2.0 allows Sync to respond to those signals. Jobs, transformations, and executions can be triggered on demand by applications, CI/CD workflows, or orchestration logic outside of Sync. Execution no longer depends on manual interaction or rigid timing. Teams get more flexibility in how and when data moves.
A stable control layer for automation
API 2.0 introduces a consistent, versioned REST interface designed for automation.
Teams can programmatically create and manage jobs, trigger and cancel runs, and monitor execution state and history. Everything available through the Sync interface is exposed through a predictable API contract, which makes it easier to standardize operations and integrate Sync into broader workflows.
This allows Sync to fit naturally into environments where infrastructure and data operations are managed as code.
Designed for AI- and agent-driven workflows
As organizations explore LLMs and agent frameworks, data movement becomes more conditional and decision-driven.
API 2.0 provides a stable control surface for these scenarios. An agent can determine when fresh data is required, trigger a Sync execution, monitor progress, and take action based on outcomes. Sync doesn’t attempt to manage AI logic. It exposes the controls that intelligent systems need to operate reliably.
Programmatic access with enterprise controls
Automation doesn’t mean giving up governance. API 2.0 respects existing workspace boundaries and role-based permissions.
Teams can tightly control who’s allowed to create, update, or execute workflows while still enabling safe automation across environments. That balance matters for enterprise teams that need flexibility without sacrificing oversight.
A natural evolution of how teams use Sync
API 2.0 complements the Sync interface rather than replacing it. Teams can continue to configure workflows visually while enabling those workflows to be controlled, embedded, and extended programmatically.
As data platforms become more automated and system-driven, API 2.0 ensures Sync fits cleanly into that operating model without forcing teams to change how they work today.
API 2.0 is part of a broader set of recent CData Sync updates focused on flexibility, automation, and modern data workflows. To see what else is new with Sync v26, read the full Sync release overview blog.
