NUCS Data Item • Limit: max. 200 documents per request
Fixed parameters for this data item (auto-filled):
mRID element)
| Name | Required | Allowed values | Description |
|---|---|---|---|
securityToken | required | — | Your API security token |
documentType | required | INFEED | |
businessType | required | A53 | A53=Planned maintenance |
periodStart | required | — | Start of the period in UTC (yyyyMMddHHmm) |
periodEnd | required | — | End of the period in UTC (yyyyMMddHHmm) |
mainAsset | optional | — | EIC of the main asset (optional filter) |
innerAsset | optional | — | EIC of the inner asset; used only together with mainAsset |
documentSender | optional | — | EIC of the document sender (optional filter) |
infeedFormat | optional | omi | omi = return the related UMM messages instead of the outage documents |
timeIntervalUpdate | optional | — | ISO 8601 interval for submissionTS filter. Use either timeIntervalUpdate OR periodStartUpdate+periodEndUpdate. |
periodStartUpdate | optional | — | Lower bound for submissionTS in UTC (yyyyMMddHHmm). Use together with periodEndUpdate when timeIntervalUpdate is not provided. |
periodEndUpdate | optional | — | Upper bound for submissionTS in UTC (yyyyMMddHHmm). Use together with periodStartUpdate when timeIntervalUpdate is not provided. |
periodStart and periodEnd are in UTC (yyyyMMddHHmm). Instead of them you can send TimeInterval as an ISO 8601 interval, e.g. 2023-01-01T00:00Z/2023-01-02T00:00Z.Unavailability_MarketDocument XML file per outage document. With infeedFormat=omi the ZIP contains the related UMM messages instead.Acknowledgement_MarketDocument (XML) whose Reason/text explains the problem, e.g. no matching data, limit exceeded or an invalid parameter combination.