Page 1 of 1

/v2/api/indigo.actionGroups

PostPosted: Fri Mar 03, 2023 1:35 am
by anyone
I should have tried this a lot sooner than I did.

It is /v2/api/indigo.actionGroups and not /v2/api/indigo.actiongroups as shown in several spots in the documentation.

Code: Select all
undefined page for request /v2/api/indigo.actiongroups from ##.###.158.98

Re: /v2/api/indigo.actionGroups

PostPosted: Fri Mar 03, 2023 6:22 am
by DaveL17
Thanks for reporting this. Yes, that is what it should be when calling the API:

Code: Select all
/v2/api/indigo.actionGroups
And when sending the API command message, it should be (no 's'):

Code: Select all
{
  "id": "optional-user-generated-id",
  "message": "indigo.actionGroup.execute",
  "objectId": 123456789
}

I've fixed the typos.

Re: /v2/api/indigo.actionGroups

PostPosted: Fri Mar 03, 2023 9:47 am
by jay (support)
Note: when in doubt (and we will fix any typos in examples when we find them), go to the Indigo Object Model docs. The messages used in HTTP and WebSocket APIs always directly use the IOM object and command class specifiers.