Sites API

With the Sites API you manage sites entirely via the API — without the pvnode web app. This is the programmatic variant of the concepts described under Sites & Strings.

Endpoints at a glance

The exact request/response schemas are in the API Reference.

Create

latitude and longitude are required. elevation, timezone and the terrain horizon are determined automatically. Without strings, a single default string is created.

curl
curl -X POST https://api.pvnode.com/v2/sites \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Roof South",
    "latitude": 48.8566,
    "longitude": 2.3522,
    "strings": [{"slope": 30, "orientation": 180, "power_kw": 10}]
  }'

Update (PATCH)

Partial update — only the sent fields change. Note:

• strings replaces the entire array. Each string has a stable, server-assigned id — echo it to keep a string (and its data, e.g. measurements); omit it and the string is dropped; send a string with no id to add a new one. The forecast strings block carries this id as string_id (plus a positional string_index), so read the site and forecast from the same point in time.
• A location change (coordinates) triggers a re-determination of elevation, timezone and horizon and invalidates the forecast cache.
• Location changes are limited to 1 per 30 days per site (plan-independent) → otherwise 429.

curl
curl -X PATCH https://api.pvnode.com/v2/sites/{site_id} \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"config": {"modules": {"technology": "topcon"}}}'

Deletion & restore

DELETE marks the site as "pending deletion" (deleted_at set); permanent removal happens 30 days later. Within this window, POST .../restore restores the site.

Limits & errors

The complete reference of all fields and error codes is in the API Reference.