I am using the GreenButtonData API sandbox and trying to authorize using datacustodian_access_token(Bearer 2a85f4bd-30db-4b7d-8f41-b046b0566cb3) but I am getting "No Authorization Found" error.
Hello, I am attempting developing an API connection using the green button this API documentation. However, all of the API tokens dont work when trying them out in this application.
None of the API calls in the sandbox seem to be working since the past few days. I am testing using the Data Custodian token and here is a sample output from one of the calls. I've also tried the batch API with subscription ID and I get the same response. Can someone please take a look and provide a resolution?We are building a sample app based on this and are presently blocked.
There is an inconsistency in the way we speak about the (6) various access_tokens. The GreenButtonAuthorization.docx defines these and we should stick with these names in all cases.
access_token: allocated by datacustodian for individual account authorizations
refresh_token: allocated at the time of authoriztion and used to renew an access_token
datacustodian_access_token: access token used by trusted administrative accounts
client_access_token: used by thirdparty applications to access bulk or multiple authorization subscriptions
upload_access_token: used by MeterDataManagement (backend) systems to upload/import data into a datacustodian
registration_access_token: reserved for future use in dynamic registration patterns
The services.greenbuttondata.org web presence has support for API testing as well as technical documentation in support of developers. Move relevant content from https://github.com/energyos/OpenESPI-wiki to incorporate into this site. Deprecate the use of the OpenESPI-wiki project.
I am using the GreenButtonData API sandbox and testing the ElectricPowerUsageSummary for user Alan (subscription ID = 5) with the access token for Alan (Bearer c59f88ed-26fb-4650-b07e-d5a031bfeb63).
When calling the ElectricPowerUsageSummary using the following API call, I see all UsagePoints 1 - 12 returned for Subscription 5.
Shouldn't this data be limited only to UsagePoint 1 given Subscription 5 has only 1 UsagePoint? Even if it had multiple usage points, the fact that I have asked for only UsagePoint 1 should be honored?
Although the "consumes" parameter value is "application/atom+xml" as required by the Data Custodian RESTful API, Swagger submits the request with a Content-Type value of "text\plain;charset=UTF-8"
Although the "consumes" parameter value is "application/atom+xml" as required by the Data Custodian RESTful API, Swagger submits the request with a Content-Type value of "text\plain;charset=UTF-8"