Skip to main content

Curves

A forward curve is a set of contracts (tenors) with a value each, for one curve date. You save a curve as a property of a master data object and read it with the Data service.

IdWhat you read
NGE.POWER.DE:BASE:2026-11-18The curve for one date (VarCurve)
NGE.POWER.DE:BASEThe list of curve dates (VarCurveDates), see Curve dates

There are four kinds of curve definition:

_typeWhat it is
VarCurveContracts and values you load for a curve date
VarSmartCurveCalculated from a base curve with an expression
VarEventCurveBuilt from the events of an event list
VarComposedCurveAn element of a composition

Smart, event and composed curves are definitions: saving one with contracts is refused.


Curve​

FieldTypeRequiredWhat it is
_typeStringYesVarCurve
_idStringNoThe data id within the object. When saved in an object, the property name is used
ondateObjectYesThe curve date: curveDate (the date) and expiryCalendar (the code of the expiry calendar that turns relative tenors into delivery periods)
contractsArrayYesThe contracts, see Contract
nameStringNoA name
descriptionStringNoA description
currencyStringNoThe currency code
unitsStringNoThe units code
timezoneStringNoThe timezone of the delivery periods, for example Europe/Berlin. It sits beside ondate, not inside it
precisionObjectNoDecimal places and rounding, see Numbers
propertiesObjectNoYour own properties
_statusObjectNoThe status of the curve
_mergeBooleanNoTrue to merge these contracts into the saved curve for the date instead of replacing it
_substitutedBooleanOutputTrue if the curve was substituted by the curve build cut-off
_identityObjectNoThe codes other systems use for the curve, by provider, see Identities. They are kept with the curve, not with each date
_objid, _dataid, _objtype, _subtypeStringOutputSet by the platform

Contract​

FieldTypeRequiredWhat it is
tenorStringYesThe tenor, as a period code: a relative code such as M01, Q01, Y01, or an absolute code such as 2026M12
valueNumberYesThe value, or "NaN" for a missing value
statusObjectNoThe status of the value
propertiesObjectNoThe standard contract properties, worked out by the platform, and your own properties, for example a vendor contract code
_typeStringOutputThe period type: Day, Week, Weekend, Month, Quarter, Season, HalfYear, Year, Balance, Custom and so on
_createdFromTenorStringOutputThe tenor the contract was sent with, when it was converted
ondateObjectOutputThe curve date, copied from the curve

An absolute tenor is stored as the matching relative tenor for the curve date: a contract sent as 2027Q01 on 2026-11-18 is stored with tenor Q01, and _createdFromTenor keeps 2027Q01.

Standard contract properties​

When a curve is saved, the platform works out these properties for every contract from its tenor, the curve date and the expiry calendar, and adds them to the contract's properties:

PropertyTypeWhat it is
absoluteStringThe absolute tenor period code of the contract, for example 2026M12
relativeStringThe relative tenor period code for the curve date, for example M01
startDateThe first day of delivery
endDateThe last day of delivery
expiryDateThe date the contract stops trading, from the expiry calendar
"properties": {
"absolute": "2026M04",
"end": "2026-04-30",
"expiry": "2026-04-27",
"relative": "M00",
"start": "2026-04-28"
}

You do not need to send them. A start, end or expiry you send is kept instead of the calculated one. For a custom tenor, start, end and expiry are the curve date.

Example​

What you send, inside an object. NGE_EOM is the expiry calendar example: contracts expire at the end of the previous month. The quarter is sent with an absolute tenor:

{
"_type": "VarCurve",
"ondate": {"curveDate": "2026-11-18", "expiryCalendar": "NGE_EOM"},
"timezone": "Europe/Berlin",
"currency": "EUR",
"units": "MWH",
"contracts": [
{"tenor": "M01", "value": 104.25},
{"tenor": "M02", "value": 109.80},
{"tenor": "2027Q01", "value": 101.15},
{"tenor": "Y01", "value": 88.40}
]
}

What you read back for NGE.POWER.DE:BASE:2026-11-18 (two contracts shown), with the standard contract properties added:

{
"_type": "VarCurve",
"_id": "NGE.POWER.DE:BASE:2026-11-18",
"ondate": {"curveDate": "2026-11-18", "expiryCalendar": "NGE_EOM"},
"currency": "EUR",
"units": "MWH",
"timezone": "Europe/Berlin",
"precision": {"roundingMode": "HALF_UP", "scale": 6, "useDefault": true, "store": false},
"_status": {},
"_identity": {"ETRM": "PWR_DE_BASE"},
"contracts": [
{
"tenor": "M01",
"_createdFromTenor": "M01",
"_type": "Month",
"value": 104.25,
"status": {},
"ondate": {"curveDate": "2026-11-18", "expiryCalendar": "NGE_EOM"},
"properties": {
"absolute": "2026M12",
"end": "2026-12-31",
"expiry": "2026-11-30",
"relative": "M01",
"start": "2026-12-01"
}
},
{
"tenor": "Q01",
"_createdFromTenor": "2027Q01",
"_type": "Quarter",
"value": 101.15,
"status": {},
"ondate": {"curveDate": "2026-11-18", "expiryCalendar": "NGE_EOM"},
"properties": {
"absolute": "2027Q01",
"end": "2027-03-31",
"expiry": "2026-12-31",
"relative": "Q01",
"start": "2027-01-01"
}
}
],
"properties": {},
"_objid": "NGE.POWER.DE",
"_dataid": "BASE",
"_objtype": "#Object",
"_oid": "NGE.POWER.DE:BASE:2026-11-18",
"_version": 1,
"_user": "priya.shah@northgate-energy.com",
"_timestamp": "2026-11-18T18:12:03.557",
"_tag": []
}

Curve dates​

When a curve is saved for a date, the platform also keeps a timeseries of the dates the curve exists for, under the curve's id without a date. Its values are references to the curve for each date. You do not save it yourself.

FieldTypeWhat it is
_typeStringVarCurveDates
_idStringThe curve's data id, for example NGE.POWER.DE:BASE
calendarStringDAILY
expiryCalendarStringThe expiry calendar of the curve
_subtypeStringThe kind of curve: VarCurve, VarEventCurve, VarSmartCurve
name, description, timezone, precisionCopied from the curve
_identityObjectThe curve's identities, added to the curve for each date when it is read
dataArrayOne value per curve date: time is the date and value a reference to NGE.POWER.DE:BASE:2026-11-18

Curve series​

A curve series (VarCurveSeries) is a curve held as a timeseries of delivery times, for example quarter-hourly power prices for the next days. It has the fields of a timeseries plus ondate, the curve date, and needs a calendar.

{
"_type": "VarCurveSeries",
"ondate": {"curveDate": "2026-11-18", "expiryCalendar": "#REOD"},
"calendar": "#PT15M",
"timezone": "Europe/Berlin",
"start": "2026-11-19T00:00:00",
"data": [96.2, 95.8, 94.9, 94.1]
}

Smart curve​

FieldTypeRequiredWhat it is
_typeStringYesVarSmartCurve
baseCurveReference or StringYesThe curve it is built on: a reference or a data id
expressionStringYesThe ODSL expression, for example BASE * 1.1 or BASE - GAS * 2
scriptStringNoA script whose functions the expression can use
name, descriptionStringNoDescriptive fields
currency, unitsStringNoThe currency and units of the result
timezoneStringNoOnly when it differs from the base curve
category, commodity, market, productStringNoClassification used to find and group smart curves
priorityIntegerNoThe build priority: 1 high, 2 medium (the default), 3 low
precisionObjectNoDecimal places and rounding
propertiesObjectNoOther inputs to the expression. A string that is a data id (it contains a colon) is turned into a reference to that data
cacheOptionsObjectNoWhen the curve is built and stored: type is Never, OnDemand, OnDependencies (the default), OnSchedule or External, and schedule is the cron schedule for OnSchedule
{
"_id": "CLEAN_SPARK_DE",
"_type": "VarSmartCurve",
"name": "German clean spark spread",
"category": "Spread",
"commodity": "Power",
"currency": "EUR",
"units": "MWH",
"baseCurve": {
"_type": "VarReference",
"_service": "data",
"_source": "private",
"_oid": "NGE.POWER.DE:BASE"
},
"expression": "BASE - (GAS / 0.49) - (EUA * 0.37)",
"properties": {
"GAS": "NGE.GAS.TTF:MID",
"EUA": "NGE.EUA:SETTLE"
},
"cacheOptions": {"type": "OnDependencies"}
}

Event curve​

An event curve builds a curve for each date from the events of an event list: one event per contract.

FieldTypeRequiredWhat it is
_typeStringYesVarEventCurve
eventStringYesThe event list, as objectid:eventlist
propertyStringYesThe event property used as the contract value
tenorStringNoThe event property that holds the tenor period code, for example relative or absolute
calendarStringNoThe expiry calendar code. Note: not inside an ondate object
holidayCalendarStringNoThe holiday calendar: the dates the curve is published on
filterStringNoA filter on the events
sourceStringNoThe source of the events
valueTransformationStringNoAn expression applied to every value, for example value * 1.1
name, description, currency, units, timezone, precision, propertiesNoAs for a curve. properties.include names event properties copied onto each contract, as well as the standard contract properties
{
"_id": "SETTLE",
"_type": "VarEventCurve",
"event": "NGE.GAS.ZTP:EVENTS",
"property": "SETTLEMENT_PRICE",
"tenor": "absolute",
"calendar": "#REOD",
"timezone": "Europe/Brussels",
"properties": {"include": "contractCode"}
}

Composed curve​

A composed curve is one element of a composition report.

FieldTypeRequiredWhat it is
_typeStringYesVarComposedCurve
compositionStringYesThe id of the composition
elementStringYesThe element (column) of the composition
name, descriptionStringNoDescriptive fields
propertiesObjectNoYour own properties

Curve management​

The Curve service keeps the management information of your curves: their configuration, the result of each day's build, and the groups that control building, quality, approval and export.

Curve configuration​

curve/v1/info

FieldTypeWhat it is
_idStringThe curve id, for example NGE.POWER.DE:BASE
_typeStringThe kind of curve
name, descriptionStringCopied from the curve
parents, childrenString[]The curves this curve is built from, and the curves built from it
buildGroupStringThe build group
qualityGroupStringThe quality group
approvalGroupStringThe approval group
exportGroupsString[]The export groups
tagsString[]Your own tags

Curve build​

curve/v1/build, one record per curve per date.

FieldTypeWhat it is
_idStringobjectid:curve:date, for example NGE.POWER.DE:BASE:2026-11-18
curveStringThe curve id
ondateStringThe curve date
statusObjectbuild, quality and approval status, with messages such as buildMessage
messageStringThe status message
scoreInteger4 no issues, 3 failed checks, 2 substituted, 1 failed, 0 holiday
scoreInfoStringAbout the score
buildsObjectEach build attempt by id: status, message, log
lastBuildIdStringThe id of the last build attempt
checksObjectThe quality checks performed
timelineString[]Everything that happened to the build
timestampDateTimeWhen it last changed
notes, tagsYour own notes and tags
{
"_id": "NGE.POWER.DE:BASE:2026-11-18",
"builds": {
"af1b4366-8752-4446-90c5-ca176eccec6f": {
"log": ["complete"],
"message": "Built by the Northgate curve engine",
"status": "built"
}
},
"status": {"build": "built", "buildMessage": "Built by the Northgate curve engine"}
}

Curve groups​

curve/v1/group. Every group has type, name and description. The other fields depend on the type:

typeFields
buildcron (the cut-off), offset (days from the cron date to the curve date, 0 or -1), useLatest (substitute the latest valid build), script (used to build a substitute when useLatest is false), calendar, timezone
qualityscript and checks, a list of {name, expression}
approvalapprovers (emails) and version (the tag put on an approved curve)
exportcron, offset, script, expression (the function to run, for example export()), calendar
{
"type": "build",
"name": "NGE_POWER_EOD",
"description": "Northgate power curves, end of day",
"cron": "30 18 * * 1-5 * Europe/London",
"offset": 0,
"useLatest": true,
"calendar": "#HENG",
"timezone": "Europe/London"
}