# Introduction to the V2 API

The **pvnode V2 API** is the next generation of our solar API. It delivers precise
PV power forecasts and historical yield data via a REST interface — now built around
**stored sites** instead of long URL parameter chains.

## What's new compared to V1?

In V1, every request was configured entirely through URL parameters
(`/v1/forecast?latitude=…&longitude=…&slope=…`). In V2 you create a **site** once
and then query it solely through its `site_id`:

```bash title="V2 Forecast API"
GET https://api.pvnode.com/v2/forecast/{site_id}
```

This brings several advantages:

- **Fixed sites** with a simple, short query — no need to repeat the configuration.
- **Multiple PV strings per site** (different orientation/tilt) in a single model.
- **`include` groups** instead of freely mixed `required_data` lists.

:::note
The V1 API remains unchanged and still available. Existing integrations keep working.
The [migration guide](/en/v2/migration) describes how to switch over.
:::

## The three building blocks

| Building block | Purpose |
|---|---|
| **[Sites](/en/v2/api/sites)** | Create and configure PV systems (geometry, strings, module technology, shading, trackers). |
| **[Forecasts](/en/v2/api/forecast)** | PV power forecast for a site, optionally with weather, irradiance, variability band. |
| **[Historical data](/en/v2/api/historical)** | Past PV yields and weather data over freely selectable time ranges. |

## Hobby vs. Pro

- **Hobby users** manage their sites through the [pvnode web app](https://pvnode.com/sites)
  and query forecasts via the API.
- **Pro/B2B users** additionally manage sites **programmatically** via the API and can use
  the [inline endpoints](/en/v2/enterprise/inline) — see
  [Enterprise](/en/v2/enterprise/index).

## Next steps

- **[Quickstart](/en/v2/quickstart)** — from API key to your first forecast in minutes.
- **[Sites & Solar Areas](/en/v2/api/sites)** — understand the data model.
- **[API Reference](/api)** — complete endpoint, parameter and field list.