Cheniere LNG Connection Pipeline Informational Postings API
The public, unauthenticated JSON API behind Cheniere's LNG Connection site, which publishes the FERC-mandated informational postings for Cheniere Creole Trail Pipeline, L.P. (tspNo 200) and Cheniere Corpus Christi Pipeline, L.P. (tspNo 400). It serves operationally available and unsubscribed capacity by NAESB nomination cycle, firm and interruptible transactional reporting, the quarterly Index of Customers, daily and comingled gas quality, posted imbalances, operational notices, and the location, station and contact reference data. 35 operations, all data operations read-only, no credential of any kind. Cheniere publishes no OpenAPI and no documentation for it; the specification in this repository was derived by API Evangelist from the provider's own client bundle plus live anonymous probes on 2026-09-06 and is labelled as derived.
Cheniere LNG Connection Pipeline Informational Postings API is one of 2 APIs that Cheniere Energy publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Natural Gas, Pipelines, FERC, NAESB, and Capacity. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, and rate-limit docs.
This API exposes 35 operations across 35 paths, organized into 10 resource areas, and defines 18 schemas. It is described by OpenAPI 3.1.0, at version 2026-09-06.
Requests are made against a single base URL, https://lngconnectionapi.cheniere.com.
Metadata
The identity and technical contract details declared by the specification.
Paths & Operations 35
Across 35 paths, the API surfaces 35 operations — 32 GET, 3 POST. They span 10 resource areas: Discovery, Capacity, Gas Quality, Transactional Reporting, Index of Customers, Imbalances, Notices, Documents, Reference Data, Telemetry. Each is listed below with its method, path, parameters, and response codes.
The posting page tree and the TSPs served.
Operationally available and unsubscribed capacity postings by nomination cycle.
Daily, comingled and mainline gas-quality analyses.
Firm, interruptible and capacity-release transactional reporting.
Quarterly Index of Customers postings.
Posted imbalance reports.
Critical and non-critical operational notices.
Documents attached to posting pages.
Locations, stations, contacts, legends and footers.
Client-side error reporting sink.
Schemas 18
The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are TransactionalReportRow (26 properties), LocationDetail (23 properties), OperationallyAvailableCapacity (20 properties), GasQualityReading (18 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 Cheniere Energy 1
Other APIs Cheniere Energy publishes across the network.
This is an independent, third-party profile of Cheniere LNG Connection Pipeline Informational Postings 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.