Suspecting the script wasn't able to access the data from the cloud, I just tried to open the API Tokens page and am getting a 404 message.... is this the same for anyone else or just me I wonder. [(https://api.givenergy.cloud/v1/account-settings/api-tokens)]
OK so I just tried removing the 'v1' part from the URL and the webpage loaded!?!
https://api.givenergy.cloud/account-settings/api-tokensAPI guide document
Wondering what was going on I headed to the API guide document (below) and that still shows the old URL, so I have not got the foggiest why this is the case. Best bet is the GE have changed / updated the API backend and not updated the documentation to match. Did I miss the memo on this???
https://api.givenergy.cloud/docs/api/v1#introduction
Mine is still working with V1 in the URL
DreadorUK Oh really, triple checked and still wont load for me. Maybe this has something to do with version/firmware of the invertor. Mine is a GIV-HY5.0 (Gen 1) running D0.449-A0.451
Have you tried a new key. The old ones created before all the "scopes & key lifetime" stuff was added just seem to expire anyway.
Mine randomly just stopped last year.
hoggy thanks, yes this turned out to be the issue. But I could only navigate to the api token page by removing the 'v1' from the weblink (as per my previous post above).
Once there I was able to reissue the new style token and add the Key to my script. Running that script (which still references the URL with the v1 in the address) saw it all up & working again. Thanks for everyone's input, and hope this chain helps others when their old tokens expire!
I am having an issue around API tokens too. My local_api_token expired yesterday. I was able to generate a new one and gave it all the scopes but the API requests I was using it for will only return in HTML form.
I was running the requests through Google Appscript but have tried in Postman and manage to get back a json response but is says simply "unauthenticated".
Should the API Key have changed with the new token and if so where can I find it? Is the authentification process different with the new tokens?
Yes if you change token old key will be linked to that
You should of seen this when creating it and copied the key then - if you didn't you will need to create another
Amazing, thank you! Didn't notice that when I created the token. It worked creating a duplicate.