Skip to main content

POST /data-service-notifications/v1/{mpid}/send

Sends an IF-024 notification to the data service for one supplier MPAN.

Supported event codes:

  • SN-Vacant
  • SN-NoComms
  • SN-RemoteEnabled
  • SN-RemoteDisabled
  • SN-OffPeakDec

Request​

Method and path:

  • POST /data-service-notifications/v1/{mpid}/send

Headers:

  • X-API-KEY (required): string, API key used for tenant authorization.
  • X-IDEMPOTENCY-KEY (required): string idempotency key.

Path parameters:

  • mpid (required): string supplier MPID.

Body schema:

  • Data service notification request object

Example: remote enable notification

{
  "mpan_core": 1234567890123,
  "event_code": "SN-RemoteEnabled",
  "supplier_notification_effective_from_date": "2026-03-20T00:00:00+00:00",
  "supplier_notification_expiry_date": null,
  "additional_information": "Remote comms restored after engineer visit.",
  "meter_id": "A1B2C3D4E5"
}

Example: off-peak declaration

{
  "mpan_core": 1234567890123,
  "event_code": "SN-OffPeakDec",
  "off_peak_declarations": [
    {
      "off_peak_declaration_date": "2026-03-19T00:00:00+00:00",
      "off_peak_declaration_proportion": 35
    }
  ]
}

Response​

Success:

  • 201 Created
  • Body: data service notification response object
{
  "message_id": "bf7bfdf1-0d15-4cf8-b72b-64d18342dff8",
  "recipients_dip_id": [
    "DIP-DIST-001"
  ],
  "status": "success",
  "sent_datetime": "2026-03-20T08:22:04+00:00",
  "mpan_core": 1234567890123,
  "event_code": "SN-RemoteEnabled"
}

Other documented responses from route logic:

  • 403 when the MPAN is not active for the supplier.
  • 404 when the MPAN is not found for the supplier.
  • 422 validation error.
  • 428 missing X-IDEMPOTENCY-KEY from shared idempotency handling.

Field-level constraints: