1. heating
Residentia REST API
  • Residentia REST API
    • location
      • getLocations
      • getLocationByLocationNumber
    • sensor
      • getSensorBySensorId
      • getSensorHistoryBySensorId
    • overdrive
      • setOverdriveSettings
      • getOverdriveSettings
      • getOneLocationOverdriveSettings
      • getLocationOverdriveStatus
    • consumption_report
      • getMonthlyConsumption
      • getDailyConsumption
      • getDistrictHeating
      • specificEnergyConsumption
    • heating
      • getLocationHeatingCurve
        GET
      • getLocationTargetSetpoint
        GET
    • Schemas
      • LocationItem
      • LocationSensorItem
      • SensorItem
      • SensorHistoryItem
      • HistoryData
      • OverdriveBody
      • Overdrive
      • OverdrivePostResponse
      • OverdriveGetResponse
      • HeatingCurvePoint
      • HeatingCurveItem
      • TargetSetpointItem
      • OverdriveStatusItem
      • MonthlyConsumptionItem
      • SpecificEnergyTypeResult
  1. heating

getLocationHeatingCurve

GET
/location/{location_number}/heating_curve
Per-circuit heating curves. Each curve is the operator's set-point knots — sparse (out_temp, supply_setpoint) pairs, ascending — not the runtime-interpolated values between them. supply_setpoint is the intended supply-water temperature in °C.

Request

Authorization
API Key
Add parameter in header
X-ApiKey
Example:
X-ApiKey: ********************
or
Path Params

Responses

🟢200
application/json
successful operation
Bodyapplication/json

🟠400
🟠403
🟠404
🟠429
🔴500
Request Request Example
Shell
JavaScript
Java
Swift
curl --location '/location/10000001/heating_curve' \
--header 'X-ApiKey: <api-key>'
Response Response Example
200 - Example 1
[
    {
        "circuit_id": 42,
        "location_number": "10000001",
        "curve": [
            {
                "out_temp": -20,
                "supply_setpoint": 58
            }
        ]
    }
]
Modified at 2026-06-18 14:38:42
Previous
specificEnergyConsumption
Next
getLocationTargetSetpoint
Built with