Differences

This shows you the differences between two versions of the page.

--- indigo_2025.1_documentation:api [2026/02/01 20:08] – [Trigger Objects] davel17
+++ indigo_2025.1_documentation:api [2026/03/23 12:52] (current) – [refresh folder server message] davel17
@@ Line 97: / Line 97: @@
 The WebSocket and HTTP APIs are designed to be familiar to those that have been using the legacy RESTful API. However, anyone with knowledge of Python, JavaScript or similar languages should be able to pick up the structure of the new APIs very quickly. To help those making the transition as well as those learning to use API calls for the first time, we've laid out several examples to show how API calls are made, as well as all the current API hooks available.
-Here's a simple Python script to open the device-feed and print out any messages it receives (you'll need to ''**pip3 install websockets**'' before running it).
+Here's a simple Python script to open the device-feed and print out any messages it receives (you'll need to ''**pip3 install websockets**'' before running it if it isn't already installed - Indigo installs it on the Indigo Server Mac so you won't need to install there).
 === Python Receiver Example ===
@@ Line 784: / Line 784: @@
 </code>
-As of this release, this is the only way to get the current state of folders (there are not add/update/delete messages). If you think you need to refresh your folder list, then send the refresh message. Since folders are generally static, there really isn't much need to continually get the folder list.
+As of this release, this is the only way to get the current state of folders (there are no add/update/delete messages). If you think you need to refresh your folder list, then send the refresh message. Since folders are generally static, there really isn't much need to continually get the folder list.
 ==== Log Feed ====
@@ Line 2348: / Line 2348: @@
 ''objectId'' is the id of the schedule.
-** enable **
+** enable ** ''[[schedule_class#enable|indigo.schedule.enable(123456789)]]''
 <code json>
 {
@@ Line 2393: / Line 2393: @@
 These are the available trigger commands. The ''id'' key is optional, but may contain a user generated ID that will be logged and returned to help match up with message requests. Custom ''id'' values should be strings.
-** execute **  ''[[schedule_class#execute|indigo.schedule.execute(123456789)]]''
+** execute **  ''[[trigger_class#execute|indigo.trigger.execute(123456789)]]''
 <code json>
@@ Line 2405: / Line 2405: @@
 ''objectId'' is the id of the trigger.
-** enable **
+** enable **   ''[[trigger_class#enable|indigo.trigger.enable(123456789)]]''
 <code json>
 {