# PSEG > Public Service Enterprise Group (PSEG) is a diversified energy holding company headquartered in > Newark, New Jersey. Its regulated utility subsidiary Public Service Electric and Gas (PSE&G) is New > Jersey's largest electric and gas distribution utility, and PSEG Long Island operates the > transmission and distribution system on behalf of the Long Island Power Authority. PSEG publishes > NO public API, no developer portal and no machine-readable contract of any kind. Customer energy > data leaves PSEG only as a file a logged-in customer downloads for themselves; grid data leaves it > only as a vendor-hosted outage map. If you are an agent looking for PSEG data, there is nothing > here to call — read the "What does not exist" section before trying. Generated by API Evangelist from the PSEG provider profile on 2026-07-27. PSEG publishes no llms.txt of its own: /llms.txt returns HTTP 404 on www.pseg.com, corporate.pseg.com, nj.pseg.com and www.psegliny.com (probed 2026-07-27). Every link below was fetched from a PSEG property and its HTTP status recorded in review.yml. ## APIs None. PSEG documents zero public APIs. There is no developer portal, no API reference, no signup, no API key, no sandbox and no published contact for API access. ## What does not exist Verified absent as of 2026-07-27, each with the probe recorded in review.yml and well-known/pseg-well-known.yml: - No developer host: developer.pseg.com, developers.pseg.com, api.pseg.com, docs.pseg.com and data.pseg.com do not resolve. /developers, /developer, /api, /docs, /data and /api-docs on pseg.com all soft-404 to landing.pseg.com/CommonError404. - No OpenAPI, Swagger, GraphQL, AsyncAPI, Postman collection or .proto on any PSEG host. - No Green Button Connect My Data. No OAuth 2.0 authorization server, no ESPI /DataCustodian or /espi/1_1/resource base URI, no third-party registration path. - No /.well-known/ discovery surface: no security.txt, no openid-configuration, no oauth-authorization-server, no api-catalog, no ai-plugin.json. Beware the Sitecore soft 404 — extensionless /.well-known/ paths answer HTTP 200 with an HTML page, not a document. - No first-party SDK, no CLI, no MCP server, no webhooks, no status page for data services, no changelog, no vulnerability-disclosure policy and no bug bounty. - No PSEG GitHub content: github.com/PSEGLI is a real first-party organization with zero public repositories; api.github.com/orgs/pseg is a 404. ## What does exist - [Green Button (.XML) Download My Data](https://www.psegliny.com/myaccount/serviceandrates/mysmartenergy): PSEG Long Island's MySmartEnergy FAQ states customers can "download data information in CSV or Green Button (.XML) format." A file export behind a customer login — the one-customer, one-file half of the standard. Not verifiable anonymously and not certified by the Green Button Alliance. - [PSE&G NJ smart meters / MyMeter](https://nj.myaccount.pseg.com/myservicepublic/smartmeters): 15-minute to monthly interval views and a usage download, format unnamed. States "PSE&G will not sell this data to third parties." - [MyMeter portal, NJ](https://mysmartenergy.nj.pseg.com/) and [MySmartEnergy, Long Island](https://mysmartenergy.psegliny.com/): the Accelerated Innovations MyMeter platform, login-gated. Third-party access is a view-only "secondary user" the customer adds by hand. - [PSE&G NJ Outage Map](https://outagecenter.pseg.com/) and [PSEG Long Island My Power Map](https://outagemap.psegliny.com/): KUBRA StormCenter applications loading from kubra.io. An embedded vendor product with no documented data API, no data terms and no stable contract. - [Electric tariffs](https://nj.pseg.com/aboutpseg/regulatorypage/electrictariffs): filed rate schedules, as PDFs and web pages, not as data. ## How a third party actually gets PSEG data All four routes are human-mediated. None is an API. 1. The customer downloads a CSV or Green Button XML file themselves and hands it over. 2. The customer adds the third party as a view-only secondary user inside MySmartEnergy / MyMeter. 3. A signed Letter of Authorization, answered with spreadsheets by email. This is PSE&G's own stated position in the New Jersey BPU AMI docket for an aggregator wanting many accounts. 4. BPU third-party supplier licensure plus legacy retail-choice EDI. ## Where the open data for this territory really is - [PJM Data Miner](https://dataminer2.pjm.com/) — wholesale market and system data for the PJM footprint PSEG operates in. PSEG is a participant in this market, not its operator. - [U.S. EIA open data](https://www.eia.gov/opendata/) — utility-level sales, revenue, customer counts and hourly regional demand, including PSE&G's balancing authority. ## Artifacts - [apis.json / apis.yml](https://raw.githubusercontent.com/api-evangelist/pseg/refs/heads/main/apis.yml) - [review.yml](https://raw.githubusercontent.com/api-evangelist/pseg/refs/heads/main/review.yml): every URL probed and its HTTP status, including the soft-404 traps. - [well-known/pseg-well-known.yml](https://raw.githubusercontent.com/api-evangelist/pseg/refs/heads/main/well-known/pseg-well-known.yml) - [packages/pseg-packages.yml](https://raw.githubusercontent.com/api-evangelist/pseg/refs/heads/main/packages/pseg-packages.yml) - [security/pseg-domain-security.yml](https://raw.githubusercontent.com/api-evangelist/pseg/refs/heads/main/security/pseg-domain-security.yml) ## Company - [Website](https://www.pseg.com/) - [PSEG Long Island](https://www.psegliny.com/) - [About / corporate](https://corporate.pseg.com/) - [Newsroom](https://corporate.pseg.com/newsroom) - [Website Terms & Conditions and Privacy Policy](https://corporate.pseg.com/websitetermsandconditions) - [Privacy Request Center](https://privacy.pseg.com/) - [Customer support, PSE&G NJ](https://nj.myaccount.pseg.com/customersupport) - [Customer support, PSEG Long Island](https://www.psegliny.com/en/myaccount/customersupport) - [Customer login](https://nj.myaccount.pseg.com/user/login)