Skip to main content
GET
/
schedule-management
/
v1
/
schedules
/
{uid}
/
delivery-status
Get Delivery Status
curl --request GET \
  --url https://api.engrate.io/schedule-management/v1/schedules/{uid}/delivery-status \
  --header 'Authorization: <api-key>'
{
  "date": "<string>",
  "nrr_received": true,
  "status": "<string>",
  "tso": "<string>",
  "mako_file_id": "MAKO-FILE-20260325",
  "nrr_checked_ts": "2026-03-25T14:10:00+00:00",
  "transmission_report_id": "TR-20260325-001",
  "tso_message_id": "TSO-MSG-20260325-001",
  "tso_message_version": 1
}

Documentation Index

Fetch the complete documentation index at: https://docs.engrate.io/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

Path Parameters

​
uid
string<uuid>
required

Schedule unique identifier.

Response

Successful Response

Delivery status tracking the AS4 delivery lifecycle between submission to Mako365/MMC Hub and ACK receipt from the TSO.

​
date
string
required

Delivery date in ISO 8601 format.

Example:

"2026-03-26"

​
nrr_received
boolean
required

Whether a Non-Repudiation of Receipt has been received from the AS4 gateway.

​
status
string
required

Delivery status: pending, nrr_received, submitted, or rejected.

Examples:

"submitted"

"nrr_received"

"pending"

​
tso
string
required

TSO identifier this delivery status relates to.

Example:

"50HERTZ_DE_TSO"

​
mako_file_id
string | null

Mako365 file identifier for the submitted document.

Example:

"MAKO-FILE-20260325"

​
nrr_checked_ts
string | null

ISO 8601 datetime when the NRR status was last checked.

Example:

"2026-03-25T14:10:00+00:00"

​
transmission_report_id
string | null

Transmission report identifier from the AS4 gateway.

Example:

"TR-20260325-001"

​
tso_message_id
string | null

TSO's authoritative message identification for this delivery date.

Example:

"TSO-MSG-20260325-001"

​
tso_message_version
integer | null

TSO's message version number.

Example:

1