Apple Watch HTTP requests

Start with an endpoint

Have a URL that performs an action? In KorkeTrigger’s iPhone app, create a profile and add an action. Choose GET, POST or PUT, enter the URL, and add Basic authentication, custom headers or a JSON or form body if your endpoint needs them. Test the action before using it from Watch.

A Home Assistant webhook, Node-RED flow or Raspberry Pi service can all be candidates when they expose a suitable HTTP endpoint. KorkeTrigger uses HTTP; it does not provide official vendor integrations.

Put the action on your Watch

Arrange actions on Watch pages in the iPhone app, then synchronize the selected profile. The Watch sends the request directly to the URL you configured. The phone does not relay it.

That makes network reachability important: a local address must be reachable by the Watch itself. An iPhone VPN, including WireGuard, does not automatically provide a route to the Watch. For a remote endpoint, check the route and DNS on the device that executes the action. Prefer HTTPS when crossing networks; use plain HTTP only where your trusted setup requires it.

Other quick surfaces

The same profile can supply actions to iPhone Home Screen and Lock Screen widgets. Lock Screen execution still follows iOS authentication requirements. You can also run configured actions from the iPhone app.