isoview-client
Python client for the ISOview energy forecasting API — demand, wind, solar, LMP, and natural gas forecasts across US ISOs, returned as dicts or pandas DataFrames.
Installation
pip install isoview-client
Requires Python 3.10+. Installs requests and pandas as dependencies.
Authentication
Sign up at isoview.io and grab your API key from the Portal.
from isoview import Client
client = Client("your-api-key")
How It Works
The client dynamically builds methods from the API's OpenAPI spec at init time. This means it automatically stays in sync with the API — no client updates needed when new endpoints are added. The spec is cached locally for 1 hour.
# See all available methods
dir(client)
# Get help on any method
help(client.get_regional_forecast)
Quick Start
from isoview import Client
client = Client("your-api-key")
# Get the latest PJM demand forecast as a dict
data = client.get_regional_forecast("pjm", "demand")
# Or get it directly as a pandas DataFrame
df = client.get_regional_forecast("pjm", "demand", as_df=True)
print(df.head())
Timeseries endpoints accept an as_df=True keyword argument to return a pandas DataFrame with a UTC DatetimeIndex and MultiIndex columns like ("pjm_total", "forecast"). Without it, you get the raw API response as a dict.
Examples
Regions
Forecasts for geographic regions within an ISO — demand, wind, solar, outages, and population-weighted temperature.
# See what regions are available
regions = client.list_regions("pjm", "demand")
# Returns a list of dicts: [{"id": "pjm_total", "name": "PJM Total", ...}, ...]
# Latest forecast as a DataFrame
df = client.get_regional_forecast("pjm", "demand", id="pjm_total", as_df=True)
# Stitched historical forecast — what did the day-ahead forecast
# look like at 10am each day?
df = client.get_region_continuous_forecast(
"miso", "wind",
start="2025-01-01T00:00:00Z",
end="2025-06-01T00:00:00Z",
latest_hour=10,
days_ahead=1,
as_df=True,
)
# Probabilistic ensemble forecast (multiple scenarios)
data = client.get_ensemble_forecast("pjm", "demand", id="pjm_total")
# Day-ahead backcast for model evaluation
data = client.get_region_day_ahead_backcast("pjm", "demand")
# Everything at once — demand, wind, solar, outages, temp, LMP
data = client.get_iso_summary("pjm")
Plants
Generation forecasts for individual wind and solar facilities.
# Browse plants in ERCOT
plants = client.list_plants("ercot", "wind")
print(plants[0]["name"], plants[0]["capacity_mw"], "MW")
# Get a forecast as a DataFrame
df = client.get_plant_forecast("ercot", "wind", id=str(plants[0]["id"]), as_df=True)
Counties
County-level electricity demand forecasts, disaggregated from regional data.
counties = client.list_counties("isone")
df = client.get_county_forecast("isone", id=counties[0]["id"], as_df=True)
Gas
Natural gas price forecasts for major trading hubs.
hubs = client.list_gas_hubs()
df = client.get_gas_price_forecast(id=hubs[0]["id"], as_df=True)
LMP
Locational Marginal Price forecasts for electricity market nodes.
nodes = client.list_lmp_nodes("pjm", "dalmp")
df = client.get_lmp_forecast("pjm", "dalmp", id=nodes[0]["id"], as_df=True)
Working with Responses
Timeseries (as dict)
All forecast, continuous, ensemble, backcast, and summary endpoints return a dict by default:
data = client.get_regional_forecast("pjm", "demand")
data["model"] # 'optimized'
data["created_at"] # datetime — when the forecast was generated
data["units"] # 'MW'
data["timezone"] # 'America/New_York'
data["time_utc"] # list of datetime objects
data["columns"] # [["pjm_total", "forecast"], ...]
data["values"] # [[1234.5, ...], ...]
Timeseries (as DataFrame)
Pass as_df=True to any timeseries endpoint:
df = client.get_regional_forecast("pjm", "demand", as_df=True)
The DataFrame has a DatetimeIndex and MultiIndex columns (e.g. ("pjm_total", "forecast")).
Metadata
List endpoints return plain dicts:
regions = client.list_regions("pjm", "demand")
for r in regions:
print(r["id"], r["name"], r["timezone"])
plants = client.list_plants("ercot", "solar")
for p in plants:
print(p["name"], f"{p['capacity_mw']} MW", p["state"])
Automatic Chunking
Requests spanning more than 365 days are automatically split into yearly chunks and merged:
df = client.get_region_day_ahead_backcast(
"pjm", "demand",
start="2023-01-01T00:00:00Z",
end="2025-06-01T00:00:00Z",
as_df=True,
)
Error Handling
The client raises requests.HTTPError on API errors (401, 403, 422, etc.):
import requests
try:
data = client.get_regional_forecast("pjm", "demand")
except requests.HTTPError as e:
print(e.response.status_code, e.response.text)
Links
- ISOview Portal — manage your account and API key
- API Documentation — full reference for all endpoints
Metadata
Release files for isoview-client 1.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| isoview_client-1.0.4.tar.gz | 8.0 kB | With provenance | Details for isoview_client-1.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| isoview_client-1.0.4-py3-none-any.whl | Python 3 | none | any | Details for isoview_client-1.0.4-py3-none-any.whl |
Total release size: 16.1 kB
Release files / isoview_client-1.0.4.tar.gz
| Download URL | isoview_client-1.0.4.tar.gz |
|---|---|
| Size | 8.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3245851c754a6e974f037d960c5b2fe8028e152dfac9db51880dbdeb8043290b
|
|
BLAKE2b-256 checksum How to use checksums |
c38912ae6f5ab0be9df9ed938f8713a0f1fd0c6459038d92af80696c960f6ba4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 24, 2026.
Transparency logRelease files / isoview_client-1.0.4-py3-none-any.whl
| Download URL | isoview_client-1.0.4-py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
31327c24b98ccec1136a8e64f56853dfefd7956992fe97578143d422d75ec253
|
|
BLAKE2b-256 checksum How to use checksums |
1c18d1d0db532c7fa1ed70e20f527d3aca59bea1b548f232971b3571c7f58271
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 24, 2026.
Transparency logSecurity for isoview-client 1.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for isoview_client-1.0.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 24, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.