The Federal Energy Regulatory Commission (FERC) is the independent United States federal agency that regulates the interstate transmission of electricity, natural gas, and oil, licenses hydropower projects, and oversees the wholesale power markets run by the seven ISOs and RTOs. FERC sits on the wholesale side of the US energy value chain — it does not regulate retail utility service, retail rates, or the customer relationship, which remain with the fifty state public utility commissions. That jurisdictional line defines FERC's API posture exactly. FERC operates a real, self-serve open data API at api.data.ferc.gov, documented at data.ferc.gov with a published OpenAPI 3.0 description, a free 40-character API key issued from a sign-up form, a 1,000-request-per-hour rate limit, and X-Api-Key header or api_key query authentication on the api.data.gov API Umbrella stack — genuinely open market and regulatory data covering the Market-Based Rate Database, FERC Form No. 552 natural gas transactions, FERC Form 556 qualifying facility certifications, Company Registration, Annual Charges, Information Collections Management, and the NEPA infrastructure schedule. FERC also runs a credentialed OAuth2 XBRL submission API at ecollection.ferc.gov for the mandated eForms filings (Form Nos. 1, 2, 3-Q, 6, 60, 552, 714). What FERC does NOT do is any part of consumer energy data — there is no Green Button, no ESPI, no consumer data right, and no individual customer usage or billing API anywhere in FERC's surface, because retail customer data is outside its statutory reach. FERC is therefore an open-market-data, zero-consumer-data regulator, and it publishes a better documented API than most of the utilities it indirectly touches.
FERC publishes 2 APIs on the APIs.io network: Open Data API and eForms XBRL Submission API. Tagged areas include Energy, United States, Energy Markets, Electricity, and Natural Gas.
FERC’s developer surface includes authentication, code examples, changelog, sandbox, developer console, developer portal, documentation, and 35 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Energy & Utilities regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
FERC's public open data API, serving the same data assets and datasets published in the data.ferc.gov Data Catalog. A Data-Assets endpoint returns the catalog and the dataset ID...
The machine-to-machine API behind FERC's mandated eForms. Credentialed filers exchange their FERC eRegistration and Company Registration username and password for a bearer token...
The full happy path against the FERC Open Data API: list the catalog, resolve a dataset ID from the nested data-sets array, read its metadata and record count, fetch the column ...
aid: ferc
url: https://raw.githubusercontent.com/api-evangelist/ferc/refs/heads/main/apis.yml
name: FERC
kind: company
description: The Federal Energy Regulatory Commission (FERC) is the independent United States federal agency that regulates
the interstate transmission of electricity, natural gas, and oil, licenses hydropower projects, and oversees the wholesale
power markets run by the seven ISOs and RTOs. FERC sits on the wholesale side of the US energy value chain — it does not
regulate retail utility service, retail rates, or the customer relationship, which remain with the fifty state public utility
commissions. That jurisdictional line defines FERC's API posture exactly. FERC operates a real, self-serve open data API
at api.data.ferc.gov, documented at data.ferc.gov with a published OpenAPI 3.0 description, a free 40-character API key
issued from a sign-up form, a 1,000-request-per-hour rate limit, and X-Api-Key header or api_key query authentication on
the api.data.gov API Umbrella stack — genuinely open market and regulatory data covering the Market-Based Rate Database,
FERC Form No. 552 natural gas transactions, FERC Form 556 qualifying facility certifications, Company Registration, Annual
Charges, Information Collections Management, and the NEPA infrastructure schedule. FERC also runs a credentialed OAuth2
XBRL submission API at ecollection.ferc.gov for the mandated eForms filings (Form Nos. 1, 2, 3-Q, 6, 60, 552, 714). What
FERC does NOT do is any part of consumer energy data — there is no Green Button, no ESPI, no consumer data right, and no
individual customer usage or billing API anywhere in FERC's surface, because retail customer data is outside its statutory
reach. FERC is therefore an open-market-data, zero-consumer-data regulator, and it publishes a better documented API than
most of the utilities it indirectly touches.
image: https://ecollection.ferc.gov/assets/images/ferc-logo/ferc%20logo.png
tags:
- Energy
- United States
- Energy Markets
- Electricity
- Natural Gas
- Grid
- Regulator
- Government
- Open Data
- Wholesale Power Markets
- Hydropower
- Oil Pipelines
created: '2026-07-27'
modified: '2026-07-27'
x-artifacts-note: No WellKnown pointer and no MCPServer pointer are wired for FERC on purpose. FERC serves no /.well-known/
document on any host (twenty probes, 2026-07-27 — see well-known/ferc-well-known.yml) and publishes no MCP server (mcp/ferc-mcp.yml
is a candidate tool surface only). Both artifacts record the absence; neither claims a capability FERC does not have.
specificationVersion: '0.23'
apis:
- aid: ferc:ferc-open-data-api
name: FERC Open Data API
description: FERC's public open data API, serving the same data assets and datasets published in the data.ferc.gov Data
Catalog. A Data-Assets endpoint returns the catalog and the dataset IDs; Details, Data, and Dictionary endpoints return
per-dataset metadata, full row data, and column definitions. Free self-serve API key, 1,000 requests per hour, X-Api-Key
header or api_key query parameter. Runs on the api.data.gov API Umbrella stack (x-api-umbrella-request-id) hosted on cloud.gov.
Verified live 2026-07-27 — an unauthenticated GET returns HTTP 403 with API_KEY_MISSING and a bogus key returns HTTP 403
with API_KEY_INVALID.
humanURL: https://data.ferc.gov/developer/gettingstarted/
baseURL: https://api.data.ferc.gov/v1
tags:
- Open Data
- Energy Markets
- Electricity
- Natural Gas
- Regulatory Data
properties:
- type: OpenAPI
url: openapi/ferc-data-api-openapi.json
- type: Documentation
url: https://data.ferc.gov/developer/gettingstarted/
- type: APIReference
url: https://data.ferc.gov/developer/apiendpoints/
- type: GettingStarted
url: https://data.ferc.gov/developer/gettingstarted/understanding-our-apis/
- type: Signup
url: https://data.ferc.gov/developer/gettingstarted/sign-up-form/
- type: Authentication
url: https://data.ferc.gov/developer/gettingstarted/api-key-usage/
- type: RateLimits
url: https://data.ferc.gov/developer/gettingstarted/api-key-usage/
- type: Support
url: https://data.ferc.gov/developer/helpandsupport/
- type: TermsOfService
url: https://data.ferc.gov/disclaimer/
- type: DataCatalog
url: https://data.ferc.gov/datacatalog/
- type: FAQ
url: https://data.ferc.gov/faq/
- aid: ferc:ferc-eforms-xbrl-submission-api
name: FERC eForms XBRL Submission API
description: The machine-to-machine API behind FERC's mandated eForms. Credentialed filers exchange their FERC eRegistration
and Company Registration username and password for a bearer token at POST /api/token (OAuth2 password grant, role=filer),
then POST a zipped XBRL submission to /api/SubmissionHistory/ExternalFiling with the company CID, report year, report
period, and form identifier. FERC documents only that write path, but the API is not write-only — a second-round probe
on 2026-07-27 found an undocumented ANONYMOUS read surface on the same host — GET /api/PublicSubmissionHistory (37,588
filing records, 10.6 MB, no key), /api/SubmissionDetail/{filingID} (accession number and attachment manifest), /api/SubmissionHistory/forms,
/api/getTestStatus, /api/faq, and the full XBRL taxonomy release history at /api/TaxonomyHistory with its taxonomy packages,
sample forms and release notes. Those endpoints are described in a DERIVED OpenAPI in this repo (FERC publishes none),
built from FERC's own production JavaScript bundle plus its published Postman collection, with every path probed live.
Verified 2026-07-27 — POST /api/token without valid credentials returns HTTP 400 with "Failed validating user in company
registration", and the credentialed endpoints (/api/claims, /api/SubmissionHistory, /api/TaxonomyRevision) return HTTP
401.
humanURL: https://www.ferc.gov/vendor-files-library
baseURL: https://ecollection.ferc.gov/api
tags:
- XBRL
- Regulatory Filing
- eForms
- Compliance
properties:
- type: OpenAPI
url: openapi/ferc-eforms-api-openapi-derived.yml
name: Derived OpenAPI 3.1 (not published by FERC)
- type: PostmanCollection
url: collections/ferc-xbrl-submission-api.postman_collection.json
- type: Documentation
url: https://www.ferc.gov/media/ferc-submission-api-step-step-guide
- type: GettingStarted
url: https://www.ferc.gov/sites/default/files/2020-12/FERC_SubmissionAPI_PROD-Step-by-step-guide_v3.1.pdf
- type: Portal
url: https://ecollection.ferc.gov/
- type: Registration
url: https://www.ferc.gov/company-registration
- type: Documentation
url: https://www.ferc.gov/filing-forms/eforms-refresh
common:
- type: OpenAPI
url: openapi/ferc-data-api-openapi.json
name: FERC Open Data API — OpenAPI 3.0 published by FERC
- type: OpenAPI
url: openapi/ferc-eforms-api-openapi-derived.yml
name: FERC eForms API — OpenAPI 3.1 derived by API Evangelist
- type: Overlay
url: overlays/ferc-data-api-overlay.yaml
- type: AgenticAccess
url: agentic-access/ferc-agentic-access.yml
- type: DomainSecurity
url: security/ferc-domain-security.yml
- type: Authentication
url: authentication/ferc-authentication.yml
- type: Conventions
url: conventions/ferc-conventions.yml
- type: ErrorCatalog
url: errors/ferc-problem-types.yml
- type: Examples
url: examples/ferc-data-api-examples.yml
- type: Examples
url: examples/ferc-eforms-api-examples.yml
- type: RateLimits
url: rate-limits/ferc-rate-limits.yml
- type: Lifecycle
url: lifecycle/ferc-lifecycle.yml
- type: ChangeLog
url: changelog/ferc-changelog.yml
name: FERC eForms XBRL taxonomy release history
- type: DataModel
url: data-model/ferc-data-model.yml
- type: Conformance
url: conformance/ferc-conformance.yml
- type: Sandbox
url: sandbox/ferc-sandbox.yml
- type: Console
url: https://data.ferc.gov/developer/apiendpoints/
name: Interactive Swagger console — authorize a key and execute every endpoint
- type: Packages
url: packages/ferc-packages.yml
name: No official SDKs — registries probed, community packages recorded
- type: AgentSkill
url: skills/_index.yml
- type: Arazzo
url: arazzo/ferc-dataset-discovery-and-retrieval.yml
name: Discover a FERC dataset and retrieve it
- type: LLMsTxt
url: llms/ferc-llms.txt
- type: Postman
url: collections/ferc-xbrl-submission-api.postman_collection.json
name: FERC-XBRL submission collection published by FERC
- type: Website
url: https://www.ferc.gov
- type: Portal
url: https://data.ferc.gov/
- type: Documentation
url: https://data.ferc.gov/developer/gettingstarted/
- type: APIReference
url: https://data.ferc.gov/developer/apiendpoints/
- type: GettingStarted
url: https://data.ferc.gov/developer/gettingstarted/understanding-our-apis/
- type: DataCatalog
url: https://data.ferc.gov/datacatalog/
- type: SignUp
url: https://data.ferc.gov/developer/gettingstarted/sign-up-form/
- type: Authentication
url: https://data.ferc.gov/developer/gettingstarted/api-key-usage/
- type: RateLimits
url: https://data.ferc.gov/developer/gettingstarted/api-key-usage/
- type: Support
url: https://data.ferc.gov/developer/helpandsupport/
- type: FAQ
url: https://data.ferc.gov/developer/helpandsupport/api-faqs/
- type: TermsOfService
url: https://data.ferc.gov/disclaimer/
- type: PrivacyPolicy
url: https://www.ferc.gov/privacy
- type: Security
url: https://www.ferc.gov/media/ferc-vulnerability-disclosure-policy
name: FERC Vulnerability Disclosure Policy v3.0 (CISA BOD 20-01)
- type: VulnerabilityDisclosure
url: security/ferc-vulnerability-disclosure.yml
- type: VulnerabilityDisclosure
url: https://www.ferc.gov/vulnerability-disclosure-policy
- type: Strategy
url: https://www.ferc.gov/about/what-ferc/digital-strategy
- type: LinkedIn
url: https://www.linkedin.com/company/federal-energy-regulatory-commission
- type: Documentation
url: https://www.ferc.gov/ferc-online/elibrary
name: eLibrary document repository (web only, no public API)
- type: Documentation
url: https://www.ferc.gov/power-sales-and-markets/electric-quarterly-reports-eqr
name: Electric Quarterly Reports (EQR) — bulk download, no public API
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
Kin Score
How this is scored →