Validate fNAV profile against grid connection capacity (Phase 5)
Applies the fNAV capacity model (§14a EnWG) for a proposed grid connection. Runs N-1 compliance check with hybrid threshold (Option C: domain default + tenant/project/scenario override). Reports technical feasibility and enforces governance gate (Option B: final status is requires_governance_decision until legalStatus=approved AND contractStatus=signed). Delegates to grid-operations.netzfahrplanGenerate for the deterministic core.
Request
- Base URL: https://api.cernion.de
- URL: https://api.cernion.de/api/grid-connection/fnav/validate
- Auth: none declared
Query parameters
Optional Cernion MCP token as URL query parameter. If provided, it overrides CERNION_TOKEN for this request. Prefer Authorization Bearer header in production to reduce token exposure in URLs/logs.
Request body
Example request
{
"gridOperatorName": "STROMDAO Netze",
"fnavProfile": {
"requestedCapacity": 5000,
"firmCapacity": 3000,
"flexibleCapacity": 2000,
"curtailmentWindow": 4,
"signalPriorityPolicy": "Netzsignal Vorrang vor Vermarktungs- und Fahrplanoptimierung",
"controlEvidenceRef": "SCADA-ATTACHMENT-42 / Fernwirknachweis 2026-05",
"contractStatus": "negotiating",
"legalStatus": "pending"
},
"n1ThresholdOverride": {
"project": 78
},
"ownerContact": "netzplanung@stromdao.de"
}Response
fNAV validation result with capacity model, N-1 check, and governance status
Changes
No recorded changes to this operation across all 2 revisions of this API.