greenbuttonalliance / openespi-greenbutton-api-documentation Goto Github PK

Now:
CRUD Operation: GET
API URL: https://services.greenbuttondata.org/DataCustodian/espi/1_1/resource/ReadServiceStatus
Access Token Required (ACUDR): DCU

== API doc needs to reflect the above three valid tokens.

The access tokens listed for Alan and Charles need updated

Alan: c59f88ed-26fb-4650-b07e-d5a031bfeb63
Charles: c1b42255-9ed2-4808-9f06-c38e39e5b3c0

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 sample UsagePoint code in the developer documentation is not a UsagePoint, but a duplicate of the previous ApplicationInfomration block

http://energyos.github.io/OpenESPI-GreenButton-API-Documentation/#accordion

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.

Request URL
https://services.greenbuttondata.org:443/DataCustodian/espi/1_1/resource/ApplicationInformation?published-max=All&published-min=All&updated-max=All&updated-min=All&max-results=All&start-index=1&depth=All

Response Body
no content
Response Code
0
Response Headers
{}

Thanks,
Rashmi

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"

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.

Response body:

<error_description>No Authorization Found</error_description>
access_denied

Am I missing something here?

We need to enforce signed certificates on both services within services.greenbuttondata.org

The input size of the access_token is too small to see the full token

Capitalization and Style - not a functional change.

link each of the access_tokens to the definition of the particular token.

Support for the UsageSummary API (Equivalent to ElectricPowerUsageSummary API)

All unauthorized status codes returned by Spring security are 401 - UnAuthorized.

The documentation indicates a 403 - Forbidden should be returned. Which is right?

(I'm thinking all the 403's should be changed to 401's and that the ESPI documentation, if any, should indicate a 401 be returned)

After giving Data Custodian Access token it giving an authentication error

<error_description>No Authorization Found</error_description>
access_denied

for GET /espi/1_1/resource/Authorization

Need to change "client_access_token" to "access_token"

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.

Here is the API call:
https://services.greenbuttondata.org:443/DataCustodian/espi/1_1/resource/Subscription/5/UsagePoint/1/ElectricPowerUsageSummary?published-max=All&published-min=All&updated-max=All&updated-min=All&max-results=All&start-index=1&depth=All

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?

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.

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.