HTTP Toolkit RTI Driver

Drive any REST API. Per-slot HTTP method, body, auth header. HTTPS supported. 50 commands + 80 feedbacks, Send + Capture against live response bodies.

Drive any REST API or HTTP-controllable device — cloud bridges, IoT gateways, smart switches, media servers, weather APIs, smart-home hubs. Per-slot HTTP method (GET/POST/PUT/PATCH/DELETE/HEAD/OPTIONS), path, body, and Content-Type. Authorization header support for OAuth/JWT/Basic auth. Automatic HTTPS via TLS handshake. Browser web UI shows full request/response traffic, lets you Send + Capture against any HTTP service to auto-author Bool/Int/Str/Enum feedbacks from response bodies.

Features: - Browser-based web UI on the processor (port 9033) — no other RTI driver has this - Live request/response traffic log — see every header and body in real time - Send + Capture — fire a request, click capture, the feedback pattern auto-populates from the response body. Saves time - 50 commands + 80 feedbacks (20 Boolean + 20 Integer + 20 String + 20 Enum) - Per-slot HTTP method (GET/POST/PUT/PATCH/DELETE/HEAD/OPTIONS), path, body, Content-Type - Authorization header support (OAuth, JWT, Basic auth) - Automatic HTTPS via TLS handshake - .driverconfig export/import — share config between sites, version-control device profiles - 15-minute trial mode — try it on real gear before buying - MAC per licence — locked to a single processor MAC, no DRM phone-home

Introduction

A general-purpose HTTP/HTTPS utility driver. Talk to any REST API or HTTP-controllable device (cloud bridges, IoT gateways, smart switches, media servers, weather APIs) by pre-defining up to 50 HTTP requests your macros can fire as "Send Slot N". Each command has its own Method, Path, Body and Content-Type. Up to 80 feedbacks (20 Boolean + 20 Integer + 20 String + 20 Enum) match against response bodies. Browser test page on port 9033.

Driver Features

Commands (TX)

Set "Number of Commands" (0-50). Each command exposes its own settings category:

• Display Name: friendly label
• HTTP Method: GET / POST / PUT / PATCH / DELETE / HEAD / OPTIONS
• Path: the URL path starting with / (e.g. /api/v1/status). The host comes from the HTTP Connection section.
• Body: request payload for POST/PUT/PATCH. Leave blank for GET/HEAD/DELETE.
• Content-Type: applied to the body. Defaults to application/json.

Macros call commands by export name "SendSlot1" through "SendSlot50". Each fires a "SLOTN_SENT" event when used.

Feedbacks (RX)

Four feedback types, 20 of each. Match patterns against the RESPONSE BODY of every command and write to sysvars. Boolean (ON + OFF), Integer (prefix extracts first int), String (prefix captures full body), Enum (pattern-to-label list, first match wins).

HTTP Specifics

• One request at a time. If a SendSlotN is fired while another request is still in flight, the new request is refused.
• 15-second timeout per request.
• Per-request connections (Connection: close). No keep-alive.
• TLS is handled by the RTI HTTP object's StartSSLHandshake(). For self-signed certs you may need to set HTTPS off and use plain HTTP on the device's LAN port.

Multiple Toolkit drivers on one processor

HTTP Toolkit can run alongside RS-232 Toolkit, TCP Toolkit, and UDP Toolkit. Each driver:

• Has its own unique driver GUID
• Defaults to a different Web Interface port (9030 = RS-232, 9031 = TCP, 9032 = UDP, 9033 = HTTP)
• Uses its own licence seed (separate keys per driver)
• Has its own sysvars, events, and macro picks in IDesign

Supported Devices

Any REST API or HTTP-controllable device that accepts a single request and answers with a text body - cloud bridges, IoT gateways, smart switches, media servers and web APIs. No particular device is certified. Tested by Smart Home Programming against a local HTTP test server. Test the trial against your own device before buying a key.

System Requirements

• Integration Designer - 11.4 or above
• RTI processor - XP-8 class (XP-3 / XP-6 / XP-6s / XP-8 / XP-8s / XP-8v)
• Processor script runtime - 24 or above

Limitations

• One request at a time. A request fired while another is still waiting for its answer is refused.
• Each request times out after 15 seconds.
• Every request opens a new connection (Connection: close); keep-alive is not used.
• Feedbacks match the response body text; JSON is not parsed into separate fields.
• One server (host and port) per driver instance.
• Enum pattern lists longer than about 250 characters may not survive a reboot. Keep lists short.
• Settings cannot be changed while the driver is running: edit Driver Properties and send the project again.
• The trial restarts each time the driver is loaded.

Related RTI drivers

• Calendar Range Trigger RTI Driver
• Elgato Stream Deck Bridge RTI Driver
• Flic Hub Trigger RTI Driver
• Macro Runner RTI Driver
• Panel Keyboard RTI Driver
• Presence Simulation RTI Driver
• Pushover Notifications RTI Driver
• RS-232 Toolkit RTI Driver
• TCP Toolkit RTI Driver
• Tesla Wall Connector WebObject Monitor RTI Driver
• Traffic Camera Viewer RTI Driver
• UDP Toolkit RTI Driver

See all RTI drivers