Skip to content

WLTE OPENAPI

Connect WLTE Devices To Your Applications

Read live device and peripheral state, control relays and RS-485 peripherals, and receive real-time online, offline, and state-change notifications.

Watch the 4-minute real-hardware demo

USE CASES

See what you can solve with it

Five of the most common integration scenarios, each mapped to a concrete technical approach, the interfaces involved, and a complete guide.

REST + WS

Monitor unattended equipment remotely

Track device connectivity and peripheral data at scale, so problems surface the moment they happen — even with no one on site.

  • Establish a baseline with REST
  • Apply online, offline, and peripheral updates over WebSocket
  • Recover critical state after reconnecting
Monitoring guide
WebSocket

Get alerted the moment power or connectivity drops

Hear about offline devices and power loss immediately, without polling and without missing the moment it happened.

  • Separate offline from power loss
  • Avoid high-frequency HTTP polling
  • Implement reconnect, dedup, and recovery
Event guide
REST + WS

Feed device data into your own SaaS

Make WLTE the infrastructure behind your product — end customers only ever see your own accounts and UI.

  • Maintain a deviceId-to-tenant mapping
  • Serve every tenant from one connection
  • Keep WLTE credentials out of customers' hands
SaaS integration guide
REST + WS

Control pumps, gates, alarms, or industrial equipment remotely

Drive real-world equipment through relay commands, and handle success, failure, and uncertain outcomes with confidence.

  • Control one or multiple relays
  • Query final results with commandId
  • Read state before retrying a timeout
Relay guide
REST + WS

Bridge existing RS-485 equipment with one GP4

Keep the hardware you already have — passthrough talks directly to existing RS-485/Modbus peripherals, no replacement required.

  • Confirm support from the Device Type Definition
  • Read and update the baud rate
  • Send passthrough data and parse responses
RS-485 guide

REST API or WebSocket?

Not sure which to reach for? Start with REST for reads and commands, then layer in WebSocket wherever you need millisecond-level change awareness.

What you needUseWhy
Show a paginated account device listRESTReturns platform-synchronized state, built for bulk display
Refresh one device on a detail pageREST or WSBoth can request a device refresh
Track online, offline, and power lossWebSocketDo not replace it with high-frequency polling
Control relays or send RS-485 dataREST or WSIdentical command semantics; pick the transport you already have
See the full comparison

GET STARTED

Move from exploration to integration

  1. 1

    Explore online

    Inspect real devices and protocol data in Playground with no tools or credentials.

  2. 2

    Verify credentials

    Use curl or Bruno to validate your API Client, permissions, and device access.

  3. 3

    Integrate on your server

    Combine REST API, WebSocket, or an SDK based on your workflow.

Docs buildVersion v1.5.8-20260814-180545-84
Copyright © 2026 WLTE