Bart,
I have been trying to tackle this for a while now and it seems that when asking api.flukso.net for sensor parameters you'd get a 502 Bad Gateway response.
Is there a problem on your behalf?
I did make sure that it's a real SSL encrypted request so that can't be the problem.
Would you be so kind and have a check on the nginx-settings please?
Could you post the equivalent curl command that triggers this 502? I've just tested the example from the Fluksometer Manual against the api and I'm getting a 200.
The request commes from a .php environment and after RTFM a lot I now also got a 200 'OK' result.
I must have messed up big time in the original .php script.
Sorry to have bothered you.
Consider this a typical IDo10 error.
geertvanbommel has written a PHP class for extracting readings out of the platform, see [1]. It's a bit dated, but it should still work against the current api. I guess if you extend this slightly, you can use it to get the sensor metadata as well.
[1] https://www.flukso.net/content/flukso-api-php-class