Version 3 has been released!

{HTTP} command

Instructs a RemoteSign to perform an HTTP GET

This is useful when playing a sound file or displaying an image file that is not already on the destination machine. By making the file available via HTTP, the RemoteSign is able to fetch the file and store it. To prevent malicious activity the command must also include a write authorization token that was provided by the RemoteSign earlier.

This is typically used to get an image or sound file onto the machine so that it can be displayed or played.

It can also be used to trigger a web hook by omitting the file name and authorization. This can be used to trigger some eternal operation, for example, using a service such as IFTTT.


{HTTP} source ␑ destinatio authtoken

  • source - Source URL of the file to be fetched
  • destination - place to put the file. A leading pipe character indicates the file should be placed relative to the application folder. If omitted no data is saved.
  • authtoken - an write authorization taken that was previously obtained from the RemoteSign. This is needed to save data.
See also:  {TOKEN} {AUTH} {PS}

Overview and list of all RemoteSign commands: API reference

Supported by:
RemoteSign Windows 3.5
RemoteSign Sequencer 3.5 (send)
RemoteSign ESP version 3.6.14 (does not support saving data)