Description: Welland Hydro-Electric System Corp is a utility services company in Ontario, Canada.
Website: https://greenbutton.wellandhydro.com/
Utility ID:
WELLAND
(this is the utility identifier you use in our API)
In order for you to request data from Welland Hydro-Electric System Corp customers, you must register with Welland Hydro-Electric System Corp as a third party company.
As part of their Green Button Connect My Data (GBCMD) program, Welland Hydro-Electric System Corp is using UtilityAPI's EE/DER Engagement Platform to allow third-party companies to request data access from Welland Hydro-Electric System Corp customers. Authorizations use the Green Button OAuth process, which means that third-parties have to be pre-registered with Welland Hydro-Electric System Corp so they can be assigned a client_id.
After registering with Welland Hydro-Electric System Corp as a third party, to request authorizations from Welland Hydro-Electric System Corp customers and test accounts, you can use any of these methods:
WELLAND
in the
url parameter or when you create a
Form.
Once a customer has authorized, you will see an Authorization appear on your dashboard and via both our JSON API and Green Button API.
When your first register as a third party, your registration status is set to Sandbox mode. This means you can only request data from test accounts, so you can try it out or start building an integration, but real customers won't be able to authorize data sharing with you yet. Welland Hydro-Electric System Corp will review your registration, then you'll get an email letting you know that you can now switch your status to Live mode in your settings.
During the OAuth authorization flow, we by default allow Welland Hydro-Electric System Corp customers to verify their identity by providing their latest bill information. However, since third parties may not have a real customer account when they start, we also offer a "test scenario" option. Third parties can pre-select which option (lastbill or test) they want their OAuth authorize request to default to by their preferred authentication choice to the scope string. In general, you'll probably only find this useful for automated testing with test accounts, since the default (lastbill) is what you probably want to use for real Welland Hydro-Electric System Corp customers.
Scope parameter format:
auth-{type}[-{value}]
Full scope string example with authentication option (percent encoded):
scope=FB%3D4_16_51%3BAdditionalScope%3Dauth-test-test_residential
Type | Can Have Value? | Description | Scope String Example |
---|---|---|---|
lastbill |
Yes |
Authenticate using a customer's latest bill date and amount. The prefill value for this authentication type is the customer's account number. |
auth-lastbill-111111111-1 |
test |
Yes | Authenticate using a specific test scenario. | auth-test-test_residential |
Since the Welland Hydro-Electric System Corp OAuth authorization flow uses their authentication system by default, that means you can't use UtilityAPI's default test usernames to manually simulate a test scenario. Instead, below we have created some special test accounts you can simulate to try out the various authentication methods (lastbill or test).
Try one with your Welland Hydro-Electric System Corp data share link
(you aren't logged into an account that has a registered Welland Hydro-Electric System Corp client)
Account # | Last Bill Amount | Last Bill Date | Equivalent Test Scenario | Description |
---|---|---|---|---|
111111111-1 |
100.0 |
2023-07-01 |
residential |
A residential customer with 1 account and 1 electric service. |
222222222-2 |
200.0 |
2023-07-02 |
commercial |
A commercial customer with 1 account and 1 electric service. |
333333333-3 |
300.0 |
2023-07-03 |
badlogin |
Simulate error where we couldn't find that customer. |
Test Account | Equivalent Test Scenario | Description |
---|---|---|
test_residential |
residential |
A residential customer with 1 account and 1 electric service. |
test_commercial |
commercial |
A commercial customer with 1 account and 1 electric service. |
test_badlogin |
badlogin |
Simulate error where we couldn't find that customer. |
To demonstrate how you can integrate the GBC OAuth authorization process into your apps and websites, we offer a demo third party website that can be configured with any GBC client, so long as it has a specific redirect_uri added. We have also created public, sandbox-only GBC clients that you can try out (see table below).
Client ID | Company Name | Pre-configured Demo Link |
---|---|---|
WELLAND_ccccccccc |
Test Company | Link |