I provided these above
Query A
Test API
Combined and as you see they are totally separte calls
I was talking about the Request headers, different tools/utilities that make rest api calls use different methodology
infinity might use one, insomnia another, curl another,postman another, some have default settings that others do not. So for example the request header for Canvas in grafana 12 shows the following.
So I went ahead and added as many as possible to Postman so that I am comparing 
to
You need to do the same with your iot endpoint to narrow down what could be the request header that might be at the root of the issue. Then if the issue still persists and you have clearly identified the issue and it is with that test api button, you then file a bug on github
Ok I see what you mean. Will try out.
Hi,
What header values did you use?
it doesn’t matter what I used because I am not fetching data from the same iot device you have. it is just a general guidance to troubleshoot as to what exactly your specific situation is.
Because you are using Infinity plugin that actually behaves like Postman (doesn’t care about CORS, accesses endpoint directly in the backend), while in case of button in Canvas Grafana initiates request and then verificatio of the CORS part is done by browser.
After you changed CORS to * in your IoT device it now works, right?
Hi,
Thanks for info very helpful.
I see it works fine from your end. Yes I changed the IoT COR to *
However I am still getting the same error! my end
Please would you be so kind as to send me the CONSOLE and NETWORK Headers information for the succesful call your end so I may compare.
I am doing no different but it seems to work from your end but not mine?
Many thanks