receiveUniqueIdPushNotification
Receives a Traceability Unique Id push notification
- application/json
Request Body
header object required
notificationId uuid requiredA UUIDv4 to uniquely identify a Unique ID push notification.
senderBPN string requiredThe business partner number (BPN) of the sender.
senderAddress uri requiredThe Eclipse Dataspace Connector (EDC) URL of the sender.
recipientBPN string requiredThe business partner number (BPN) of the receiver.
classification string requiredPossible values: [
Child-Relationship
]The classification defines the type of the Unique ID push notification.
content object required
information stringPossible values:
<= 1000 characters
listOfItems object[] required
oneOf- MOD1
- MOD2
manufacturerId string requiredThe Business Partner Number (BPNL) of the manufacturer of the serialized part, i.e., the companies main entry.
manufacturerPartId string requiredThe ID of the type/catalog part (of which the serialized part is an instance of) from the manufacturer.
customerPartId stringThe ID of the type/catalog part (of which the serialized part is an instance of) from the customer.
partInstanceId string requiredThe serial number of the serialized part from the manufacturer. We assume here that the customer does not have or create its own serial number for a part, but just used the manufacturer's serial number.
catenaxId string requiredCatena-X ID for a serialized part.
manufacturerId string requiredThe Business Partner Number (BPNL) of the manufacturer of the batch, i.e., the companies main entry.
manufacturerPartId string requiredThe ID of the type/catalog part (of which the batch is an instance of) from the manufacturer.
customerPartId stringThe ID of the type/catalog part (of which the batch is an instance of) from the customer.
batchId string requiredThe serial number of the batch from the manufacturer. We assume here that the customer does not have or create its own serial number for a batch, but just used the manufacturer's serial number.
catenaxId string requiredCatena-X ID for a batch.
- 201
- 400
- 401
- 403
- 405
- 409
- 422
Notification was received successfully
Request body was malformed
Not authorized
Forbidden
Method not allowed
Could not accept the send notification, because a notification with that notificationId already exists
Could not accept the send notification even though it is syntactically correct. The notification is not accepted, because of semantic reasons (e.g., an item is not known by the receiver).