DriftOps Documentation
Everything you need to monitor schema drift across EDI, JSON, and API integrations.
DriftOps watches your data contracts and tells you when something changes. You define what a document should look like, then DriftOps flags any incoming file that deviates from that baseline. Every change gets logged, classified by severity, and routed to your team.
It works with EDI X12, JSON, XML, and flat-field formats. Sources include manual file uploads, webhook-based monitors, and automated cloud storage polling across S3, Azure Blob, GCP, SFTP, and FTP.
Getting started
Quick Start
Create your first contract and run a comparison in under 5 minutes.
Core Concepts
Understand contracts, comparisons, drift events, monitors, and cloud connections.
Integrations
Connect S3, Azure Blob, GCP, SFTP, Slack, and webhook sources.
Public API
Give partners read access to your contracts via API keys.
Key concepts
Contract
A contract is a saved schema definition that serves as the baseline all incoming files are compared against. When you upload a sample file, DriftOps extracts the full field structure and stores it. Contracts are versioned, giving you a complete history of how a schema has evolved. You can view, compare, and revert to any prior version at any time.
Drift Event
A drift event is created when a comparison detects differences between an incoming file and a linked contract. Each event records the full field-level diff, a severity classification of trivial, minor, or major, and a status that tracks how your team is handling it. Status options are pending, resolved, ignored, or rejected. All events accumulate in the Drift Inbox where they can be reviewed, actioned, and filtered by contract, severity, or date range.
Monitor
A monitor is a dedicated webhook endpoint linked to a specific contract. Each monitor is assigned a unique, cryptographically random token that forms its URL. When a trading partner or upstream system posts a file to that URL, DriftOps automatically parses the file, compares it against the contract, and creates a drift event if any differences are detected. Monitors remove the need for manual comparisons and integrate directly with existing file delivery workflows.