How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Toronto Hydro

Toronto Hydro Application Information API

Application Information endpoints

Documentation Provider Profile APIs.io OpenAPI GitHub

Toronto Hydro Application Information API is one of 5 APIs that Toronto Hydro publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include ApplicationInformation. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a getting-started guide.

This API exposes 2 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://sandbox.greenbuttonalliance.org:8443/DataCustodian.

2 operations 2 paths 5 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Server
https://sandbox.greenbuttonalliance.org:8443/DataCustodian
Authentication
OAuth 2.0
Contact
Green Button Alliance
License
Apache 2.0
Resource Areas
1

Authentication & Security 1

Toronto Hydro Application Information API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode and clientCredentials flows. By default, every request must be authenticated.

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

ApplicationInformation 2

Application Information endpoints

GET
/espi/1_1/resource/ApplicationInformation
Retrieve all Application Information [FB33]
findApplicationInformations 7 params → 200202400403
GET
/espi/1_1/resource/ApplicationInformation/{applicationInformationId}
Retrieve Application Information by Id [FB3]
getApplicationInformation 1 param → 200202400403

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are ApplicationInformation (12 properties), AtomEntry (6 properties), AtomFeed (5 properties), AtomLink (3 properties). Each schema is shown below with its type and property counts.

AtomContent
object
Atom content element containing ESPI resource (RFC 4287)
1 property
AtomEntry
object
Atom feed entry (RFC 4287) containing ESPI resource
6 properties
AtomLink
object
Atom link element (RFC 4287)
3 properties
ApplicationInformation
object
Contains information about a Third Party Application requesting access to DataCustodian services
12 properties
AtomFeed
object
Atom Feed (RFC 4287) containing ESPI resources
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

toronto-hydro-applicationinformation-api-openapi.yml Raw ↑

Other APIs Toronto Hydro publishes across the network.

Toronto Hydro Green Button Download My Data
AE Profile APIs.io
Toronto Hydro Authorization API
AE Profile APIs.io
Toronto Hydro Batch API
AE Profile APIs.io
Toronto Hydro Usage Point API
AE Profile APIs.io
#ApplicationInformation
← Back to T APIs
API Details
ID
toronto-hydro:toronto-hydro-applicationinformation-api
Server
https://sandbox.greenbuttonalliance.org:8443/DataCustodian
Docs
https://www.torontohydro.com/for-home/green-button
Provider
Toronto Hydro
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=toronto-hydro-applicationinformation-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/toronto-hydro-applicationinformation-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Toronto Hydro Application Information API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.