Use any zip code within ConEd territory, such as 10040, to specify ConEd as the utility in Connect. ConEd uses utility account numbers, rather than username and password, to authorize access to utility accounts. The authorization flow is as follows:
- The customer is asked to supply their utility account number to Connect
- Arcadia requests access to the utility account from ConEd on your behalf
- ConEd emails the customer asking them to grant or deny access
- Utility account data will begin to flow shortly after the customer grants access
Please note that real ConEd accounts currently can only be authorized when using thelive API mode We recommend performing ConEd testing using ConEd test account numbers below which can be re-used repeatedly (after deleting the associated user that gets created). The special ConEd account numbers are available for testing purposes. When used, Arcadia will automatically return data as if a user clicked the approve button within the triggered ConEd authorization email. The 11-digit account numbers contain several components that correspond to different parts of the available test behavior, which are described in the tables below.
| Scenario number | Account configuration | Utility statements available? |
|---|
| 0001 | Active electric account | Yes |
| 0002 | Active gas account | No |
| 0003 | Closed electric account | No |
| 0004 | New electric account | No |
| 0005 | Encounters an error gathering Utility Account details | No |
| 0006 | Encounters an error discovering historical Utility Statements | No |
| 0007 | Active commercial electric account | Yes |
| Credential status number | Result |
|---|
| 0001 | The credentials will be verified and the data corresponding to the specified scenario will become available |
| 0002 | The credentials will be rejected |
| 0003 | The credentials will behave as if a credential verification error occurred |
| Credential timeout | Description |
|---|
| 0 | No timeout delay |
| 1 | The credential verification response will be delayed until after the Connect front-end component times out |