Have you looked to see what is actually being sent to the API rather than what is consumes? The CLI accepts YAML so it is probably rather relaxed about the JSON it consumes.
GENERAL ANNOUNCEMENT
I’m pleased to announce that we’ve found a more stable hosting solution for the API Browser+, with huge thanks to @h0ckeysk8er. He has very kindly volunteered to let me host this on his AWS server. In general, you should see no difference other than the new URL, which we no longer have to worry about it changing. It’s great to have a more robust server where this can run and I can finally stop worrying about my own internet or power disruptions knocking this offline 
.
THANK YOU @h0ckeysk8er for your generousity and help in getting this all set up !!! 
New permanent URL is: https://api-browser-plus.pinsky.us/
I have a suggestion Tod for the Browser ÷
Is there a need for a system check option ?
One button on the Browser+ page that returns a list of revelant details
You currently have …
Xxx online devices
Xxx off line devices
Xxx Total connected devices
Xxx Rooms created
Xxx Automations created
Xxx Scenes created
Would be a nice quick way to return an overall view of a system, if each item in the presented list was a hyperink to the relevant Browser+ page that could also be helpful
What a nice list Graham, i mean its a bit 1980s terminal ugly but a very nice a useful overall snapshot, the fact the ST app should have a similar option as standard along with many other enhancements is probably never going to happen but if Tod feels it is within the scope of the Browser+ it would be much appreciated
That is actually a rolling log of data being read from the API and processed and it gets hidden once it is finished. It is largely diagnostic for the app rather than being useful in real terms, unless a line appears that isn’t boring green. The actual displayed data would be at home in the late 1960s. It is what I call my Ironic UI.
I’d expect to see the app start flagging offline devices as it does low batteries. I’m slightly surprised that it hasn’t already happened given how aggressive the app is about offline devices.
A think a summary is useful if you know what the numbers should be, but not terribly interesting otherwise.
As a microcomputer user going back to the TI-99/4A and the Xerox 16/8 CPM machines, sometimes “terminal ugly” is all you really need. 
The API browser is a fantastic tool, and I can’t repeat that enough.
But I’m going to ask for something that as a user I don’t know if is possible with the API, but here we go.
Could you find a way to extract, list, or view in each device, which rules each device takes part in? In the app that view is available for each device, in the Routines tab, but for those trying to use rules it’s like working in the dark.
That is certainly possible with the API as I’ve been doing it for the last three years or so (my particular goal was to detect Rules using deleted devices). However I take the brute force approach of loading all the devices and then walking all the Rules and cross-referencing them. There may be a more elegant way of doing it.
In the legacy platform it was all done by reading app subscriptions, with webCoRE also faking subscriptions for devices it used but didn’t subscribe to. The current platform isn’t so open.
Sure, that’s a great suggestion. I’ll try to get to it this week.
Had another idea for the browser. Would it be possible to have an option to display the actual API calls that the browser is making? From another thread, it would be nice to point someone to the browser to help them know which API call to use.
I’m thinking about this one. Since some actions result in numerous fetches, there would have to be a separate window or scrollable field to allow you to browse through them.
An easier answer to this one would be to just use the browser tools to display the network activity.
Fair enough. Was just thinking of folks who might not be that familiar with the developer tools in the various browsers.
How come my second gen hub is offline despite of passing the hub app and Wi-Fi except for the cloud?
The driver part is also grayed out.
Hello TAustin,
I’d apreciate a lot ussing this tool but
“Http error 403” when I try to access to
https://api-browser-plus.pinsky.us/ with my token from Spain.
Is it a known error?
Thanks in advance for your support and congratulation for the tool
Have you tried it again since you first got this error? I noticed I had to re-enter by token today, so am wondering if something temporary happened with the server.
I’m sorry but I don’t understand your question. Maybe the English translation didn’t work so well this time Can you try to re-phrase your question?
Hi TAustin,
Thanks again for your prompt replay.
I tested again but did not succeed.
What solved the issue was when I asked for a new token. Now the tool works fine 