Onetrail

...

TPN REST Communication

Onetrail TPN™ TPN is providing services in order to trade electronically by using REST. This page describes the specifications for these REST services. Onetrail TPN REST solution requires no 'Pulling' of messages. Choosing this communication, Suppliers and Buyers can POST messages to a Onetrail endpoint, and Onetrail will provide responses back to customer endpoint. It's not yet supported to collect messages from a Onetrail endpoint via REST.

Scope

The Onetrail TPN™ TPN REST for Sellers supports receiving orders, sending order status, despatch advice and invoice messages as well as handling of real-time price and availability requests. The provisioning of product-, price-, and stock data (batch) is not supported via REST, but via SOAP, FTP or email only.

The Onetrail TPN™ TPN REST for Buyers supports the real time price and availability.

Design

The Onetrail TPN™ TPN REST ODE Service for Sellers is payload agnostic, meaning the service is generic for all order related message types and thus not aware of the content of the message. Message validation (schema validation in case of XML) needs to be performed outside of the service. At this moment Onetrail TPN™ is not supporting JSON formatted messages, but only XML and EDIFACT.

...

Message definitions

Onetrail TPN™ TPN supports JSON (P&A only), XML and EDIFACT for the REST services. The documentation and definitions can be found here: Message Types

Communication

From Seller to Onetrail

...

TPN

https://$base_url/exchange/rest/tradingpartner/{toGLN}/msgtype/{msgType}/msg/{msgID}

...

• Method: POST
• Body: XML or EDIFACT content

From Onetrail

...

TPN to Seller

https://$base_url/tradingpartner/{fromGLN}/msgtype/{msgType}/msg/{msgID}

...

• base_url:
  • Acceptance: to be provided by the Seller
  • Production: to be provided by the Seller
• Variables:
  • {fromGLN} = GLN for the buyer sending the message
  • {msgType} = Order
  • {msgID} = the unique messageID
• Method: POST
• Body: XML or EDIFACT content

From Buyer to Onetrail

...

https://$base_url/pde/rest/v5/products?{SellerGLN}&{PDINumber}&{SellerVPN}&{GTIN}&{Quantity}&{BidID}

Example: https://services.onetrail.net/pde/rest/v5/products?SellerGLN=8714253023236&PDINumber=C7978A

• base_url:
  • Acceptance: acc-services.onetrail.net
  • Production: services.onetrail.net

• Variables:
  • SellerGLN (multiple ; separated)= provide the GLN from the Seller
  • PDINumber = Onetrail TPN™ PDI number
  • SellerVPN = Seller Vendor part number
  • GTIN = Seller Global Trade Item Number (EAN)
  • Quantity = Quantity for which you want the price and availability
  • BidID = Contract ID for the price of a contract product

• Remarks:
  • At least one of the product numbers is mandatory;
  • Multiple product number types can be specified and will be used in the query independent of the other, so they will be performed individually. If the results relates to the same product, only that product will be returned.
  • Buyer GLN is identified by basic authentication

• Response:

If no Seller GLN is specified, the response will contain all products from Sellers that matches the Request of which the buyer has prices

• Remarks:
  • The JSON response is based on the PRD version 3.1 output
  • The result can contain multiple Onetrail PDI items. In that case the response will contain n-times an ns2:product element
  • The result can contain multiple Seller items per Onetrail PDI item. In that case the response will contain n-time an ns2:sellerInfo element

• Method: GET
• Body: JSON content

...

TPN (Order)

https://$base_url/exchange/rest/tradingpartner/{toGLN}/msgtype/{msgType}/msg/{msgID}

...