The Orderful API is built around transactions.

A transaction represents a business document (e.g., Purchase Order, Invoice, Advance Ship Notice) that flows between you and your trading partners through Orderful.

What's in a Transaction?

Every Transaction contains the following elements:

SenderId - The ISA ID of the document sender
ReceiverId - The ISA ID of the document receiver
stream - can be live or test. Use test until you are ready for live production trading
type - The Transaction Type
message - this the the main body of the request. See Mosaic Schemas in the left panel for example payloads of each of the transaction types.

Additionally, the HEADER of the API request should include the key orderful-api-version. The current version is v4

Which Transaction Types will I need to support?

The most common transaction types for retail are the four transaction types that make up the "Order to Cash / Procure to Pay" Workflows