Data Submission API
Post real-time and historical tag data from any field device, controller, or SCADA system into Waterly. One endpoint accepts device identity and an array of named measurements with timestamps.
WaterlyConnect is the data integration layer between your field hardware, industrial gateways, and Waterly's cloud platform. One REST endpoint. One JSON payload schema. Works from Node.js, Python, PowerShell, Ignition, or any device that can make an HTTP request.
WaterlyConnect has one endpoint and one schema. The shortest path to your first accepted submission.
Contact Waterly support to receive your submission URL, client token, device id, and device type.
Choose the client or gateway guide that matches your environment — SDK, script, or importable project archive.
Submit a few tag readings to confirm your device identity and token are accepted by the WaterlyConnect endpoint.
Wire a timer, cron job, or gateway event to submit on your preferred interval — typically every 5–15 minutes.
Data submission for field devices. Identity sync for organizations managing external user directories.
Post real-time and historical tag data from any field device, controller, or SCADA system into Waterly. One endpoint accepts device identity and an array of named measurements with timestamps.
Implementor contract for organizations that maintain their own user directory and want Waterly to sync users and role assignments bidirectionally. Your system exposes these endpoints; Waterly calls them.
SDKs for server-side jobs, scripts for operational automation, and gateway projects for plant-floor submissions.
TypeScript/JS package for server-side adapters, ETL jobs, and integration services.
Zero-dependency single-file module for scripts, cron jobs, and lightweight services.
Windows-native cmdlets for operator-driven scripts and Task Scheduler automation.
Importable project archive for scheduled gateway submissions from Inductive Automation Ignition.
Script module and CSV tag list using VTScada's native HTTPSend. Configure tag schedules in a CSV file — no external server needed.
On-device BASIC script for Flexy 205 edge gateways — no external server required.
Running something else — Allen-Bradley, Modbus, FactoryTalk, a custom data historian? The API is open. We can help build it.
Reach out to the Waterly team to receive your submission endpoint, client token, and device identity. Support is also available for rollout questions and environment-specific configuration.