TI-API: Push API specifications of ASN

Hi Paul,

If there is only one notification, which PO number will be included in "customerPurchaseOrderNumber" located at the root in the json file?

It is an additional question.
If there are multiple "waybill numbers", will each receive a separate push notification?
Also,
Regarding ORDER push notifications, if there are multiple POs, will there be separate push notifications for each?

Can you clarify which API you are asking about? Your email address is associated to a TI store API suite, which does not have an order push API. For the store API, the PO information is not in the header, but within the bookingOrderDetails element that can include an array of PO numbers.

Thanks,
Paul

Paul,

Backlog-api.
We are currently considering the PUSH API.

edpsinfo,

I understand that the backlog ASN push notification payload should also align with my description above for the store ASN push - No PO information should be present in the payload header, but within bookingOrderDetails element. The ASN push specification at https://www.ti.com/swc/developer-apis/backlog/advanced-ship-notice-push-api.html is correctly showing the bookingOrderDetails containing the PO data:

...but it looks like the specification is including the request response payload in the header instead of the push payload. The ASN retrieve specification indicates that any of orderNumber, customerPurchaseOrderNumber, or wayBillNumber may be present in the header because each of those items can be the object of your retrieve query. I'll check with the team on updating the spec for the push API to indicate that only wayBillNumber would be present in the header.

In general, the API responses should always be in the context of what was requested. If you query the ASN API by waybill number, you will receive all orders that shipped on that waybill, and waybill will be in the payload header. Similarly, if you query the ASN API by customer PO number, the response will include the PO number in the header and all waybill(s) that were created for shipment. The push payload should behave similarly in that the key data that triggers a notification will be in the header and the rest of the payload will include the other pertinent details.

Regarding the order push scenario, if multiple orders ship with the same waybill, then each order will receive a push notification indicating that the order has shipped.

When a single order is shipped in multiple shipments, then multiple ASN notifications will be sent as each shipment is made.

Best regards,
Paul

Paul,

>I'll check with the team on updating the spec for the push API to indicate that only wayBillNumber would be present in the header.

Please check.

edpsinfo,

The specs should be updated by next week. Thanks for pointing out the issue.

Best regards,
Paul