emazys API

Teams plan

Read your team's sites and string test results from your own software.

Your first call

  1. Make a key

    In the emazys cloud, open Integrations and choose emazys API. A Team Admin or Data Manager switches it on and makes a key. Copy the key straight away: it is shown only once.

  2. Ask who the key belongs to

    Put the key in the X-API-Key header.

    curl -H "X-API-Key: emz_your_key" \
      {origin}/api/v1/team

    You get

    {
      "team": { "id": 12, "name": "Acme Solar" },
      "key": { "name": "Power BI", "prefix": "emz_Ab3dE9fG" }
    }
  3. Read the measurements

    Ask for up to 500 at a time. Each answer ends with next_cursor: send it back to get the next page, until it is null.

    import requests
    
    URL = "{origin}/api/v1/measurements"
    KEY = {"X-API-Key": "emz_your_key"}
    
    rows, params = [], {"limit": 500}
    while True:
        page = requests.get(URL, headers=KEY, params=params, timeout=60).json()
        rows += page["data"]
        if page["next_cursor"] is None:
            break
        params["cursor"] = page["next_cursor"]
    
    print(len(rows), "measurements")

    To fetch only what is new, add measured_after with the newest measured_at you already have.

The basics

Address
{origin}/api/v1
Key
In the X-API-Key header of every request. One key per program, so you can stop one without the others.
Answers
JSON. Times are in UTC, temperatures in °C, and a missing value is null.
Read only
Nothing can be changed or deleted through the API.
Whose data
Everything your team measured, and your team's sites.
Limit
120 requests a minute per key.

Routes

Every route is a GET request with your key.

GET/api/v1/team

The team the key belongs to, and the key's name. A quick way to test a key.

GET/api/v1/sites

Your team's sites, by name.

You can send

searchPart of a site's name or address.
limitHow many sites, 1 to 500. Default 100.
offsetHow many to skip, for the next page.

You get

{
  "data": [
    {
      "id": "site_70c4f622604d",
      "name": "Solpark Nord",
      "address": "Solvej 4, 5260 Odense",
      "latitude": 55.3601,
      "longitude": 10.4207,
      "site_type": "utility",
      "capacity_kw": 4800.0,
      "created_at": "2026-03-02T09:14:00Z",
      "updated_at": "2026-10-14T12:01:00Z"
    }
  ],
  "total": 35,
  "limit": 100,
  "offset": 0
}
GET/api/v1/measurements

Your team's measurements, oldest first, a page at a time.

You can send

site_idOnly this site. The id from /sites.
measured_afterOnly tests taken at or after this time, for example 2026-10-01T00:00:00Z.
measured_beforeOnly tests taken before this time.
limitHow many, 1 to 500. Default 100.
cursorThe next_cursor of the previous page.

For example

curl -H "X-API-Key: emz_your_key" \
  "{origin}/api/v1/measurements?measured_after=2026-10-01T00:00:00Z&limit=500"

You get, shortened (every field is under What each field means)

{
  "data": [
    {
      "id": "d2c4da31-1274-462b-a78e-5f0c9a1b7e21",
      "measured_at": "2026-10-14T09:42:10Z",
      "site": { "id": "site_70c4f622604d", "name": "Solpark Nord" },
      "string_name": "INV 3 S12",
      "voc_v": 1189.6,
      "isc_a": 11.2,
      "riso_mohm": 38.6,
      "riso_above_range": false,
      "fault_position": null,
      "rs_ohm": 7.9,
      "status": "ok",
      "status_text": "OK",
      "web_url": "https://data-cloud.emazys.com/measurements/d2c4da31-...",
      ...
    }
  ],
  "next_cursor": "MjAyNi0xMC0xNFQwOTo0MjoxMHw4ODIx"
}
GET/api/v1/measurements/{id}

One measurement, with the same fields as above plus its IV curve: a list of points, or null when the test has no curve.

You get, at the end

  "iv_curve": [
    { "voltage_v": 0.0, "current_a": 11.21 },
    { "voltage_v": 19.6, "current_a": 11.2 },
    ...
  ]

What each field means

The fields of one measurement, as /measurements sends them.

FieldUnitMeaning
When and where
idThe measurement's id. Use it with /measurements/{id}.
measured_atUTCWhen the test ran.
siteThe site's id and name, or null.
latitude, longitudedegreesWhere the phone was during the test.
operatorWho ran the test.
device_serialThe tester's serial number.
The string
string_nameThe string's name, as typed in the field.
modules_in_stringModules in series.
strings_in_parallelStrings measured together.
moduleThe PV module: maker and model.
pv_module_idThe id of the PV module this test used: the test's own module, otherwise the site's. module holds its make and model.
Sun and temperature
irradiance_w_m2W/m²Sunlight on the modules.
rear_irradiance_w_m2W/m²Light on the back of bifacial modules, from an INDEX sensor. Null when the test had none.
cell_temperature_c°CTemperature of the modules.
ambient_temperature_c°CAir temperature.
Readings
voc_vVOpen-circuit voltage.
isc_aAShort-circuit current. When the test stopped at its limit, it is null and isc_note says why.
riso_mohmMΩIsolation resistance. Above 499 MΩ it reads 499 and riso_above_range is true.
fault_positionWhere an isolation fault is, for example "Module 5" or "Homerun Cable". Null when there is none.
rs_ohmΩSeries resistance of the string.
vmpp_v, impp_a, pmax_wV, A, WThe maximum power point.
fill_factor_pct%How square the IV curve is.
Compared with the datasheet
voc_stc_v, isc_stc_aV, AVoc and Isc corrected to standard test conditions.
voc_deviation_pct, isc_deviation_pct%How far they are from the datasheet.
rs_expected_ohmΩThe series resistance the string should have.
rs_deviation_pct%How far the measured value is from it.
AI Analysis
statusok, check, fault or unknown. Null when the test has no analysis, for example an imported result.
status_textThe same in words: OK, Worth Checking, Fault Detected or Can't judge.
Other
noteThe technician's note.
web_urlThe measurement in the emazys cloud.

Errors

Every error answers {"detail": "..."} with what went wrong.

CodeWhat happenedWhat to do
400The cursor is not one we sent.Send next_cursor exactly as you got it.
401No key, or the key was deleted.Check the X-API-Key header, or make a new key.
403The API is switched off for your team, or the team's Teams plan has ended.A Team Admin or Data Manager switches it on under Integrations.
404The site or measurement is not your team's.Check the id.
422A value you sent is not valid, for example a date that is not ISO 8601.The answer names the value.
429More than 120 requests in a minute.Wait a minute, then try again.

For tools

Postman, Power Automate and code generators can read every route from openapi.json.