OEB Regulatory Document Search (RDS)
The OEB's public regulatory document search, serving every filing, decision, order, licence, code amendment and piece of correspondence in the Board's case record. It runs on Micro Focus / OpenText Content Manager WebDrawer, and the OEB links directly to parameterised query URLs of the form /CMWebDrawer/Record?q=CaseNumber=EB-2021-0183&sortBy=recRegisteredOn-&pageSize=400 from its own website — the licensed-companies list alone links hundreds of them. Fetched anonymously on 2026-07-27, this surface also honours a `format=json` parameter and returns application/json — a Content Manager ServiceAPIModel payload with Results, TotalResults, Count, HasMoreItems and typed Fields including CaseNumber, SIDocumentType, Applicant, EnergyType, PrimaryApplicationType and DateIssued — while /CMWebDrawer/Record/{uri}/File/document returns the underlying PDF. IMPORTANT — the OEB publishes no API reference, no base-URI statement, no query-syntax documentation, no OpenAPI and no terms for this interface; the JSON output is default behaviour of the underlying WebDrawer product, not a product the OEB documents or supports. It is recorded here because it was verified live and anonymous, not because it is an offered API. No key, no signup, no rate-limit policy published.
OEB Regulatory Document Search (RDS) is one of 2 APIs that Ontario Energy Board publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 1 JSON Schema definition.
Tagged areas include Regulatory, Document Search, Filings, Decisions, and Licences. The published artifact set on APIs.io includes API documentation, an API reference, an OpenAPI specification, authentication docs, and 1 JSON Schema.
This API exposes 5 operations across 5 paths, organized into 2 resource areas, and defines 7 schemas. It is described by OpenAPI 3.1.0, at version 2026-07-27.
Requests are made against a single base URL, https://www.rds.oeb.ca/CMWebDrawer.
Metadata
The identity and technical contract details declared by the specification.
Paths & Operations 5
Across 5 paths, the API surfaces 5 operations — 5 GET. They span 2 resource areas: Records, Search Metadata. Each is listed below with its method, path, parameters, and response codes.
Search and retrieve records (filings, decisions, orders, licences, correspondence) in the OEB case record.
The machine-readable query vocabulary the RDS search form itself loads.
Schemas 7
The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are RecordSearchResponse (11 properties), RecordFields (7 properties), Record (6 properties), TrimDateTime (5 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Ontario Energy Board 1
Other APIs Ontario Energy Board publishes across the network.
This is an independent, third-party profile of OEB Regulatory Document Search (RDS), 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.