papiNet API 3.0.0 Released!

The papiNet Central Work Group is pleased to announce the official release of the papiNet API 3.0.0! This release contains a completely new set of API endpoints focusing on the Warehouse Logistics use case. You should not see this 3.0.0 release as an evolution of 2.0.0, but as a sibling work introducing logistic concepts. We will later merge 3.0.0 with the previous releases, 2.0.0 remains for now fully relevant in the context of the Purchase Order use case.

Changelog

Additions

• GET /supplier-orders
• GET /supplier-orders/{supplierOrderId}
• GET /logistics-delivery-notes
• GET /logistics-delivery-notes/{logisticsDeliveryNoteId}
• POST /logistics-delivery-notes
• PUT /logistics-delivery-notes/{logisticsDeliveryNoteId}
• POST /logistics-goods-receipts
• PUT /logistics-goods-receipts/{logisticsGoodsReceiptId}
• GET /delivery-instructions
• GET /delivery-instructions/{deliveryInstructionId}

Deletions

• GET /locations
• GET /locations/{locationId}
• GET /parties
• GET /parties/{partyId}
• GET /customer-articles
• GET /customer-articles/{customerArticleId}
• POST /purchase-orders
• GET /purchase-orders
• GET /purchase-orders/{purchaseOrderId}
• PATCH /purchase-orders/{purchaseOrderId}

Clarifications

Our initial approach will be to start with a simplified operational structure, which assumes that the supplier has already defined the necessary seller-products, customer-articles, parties, and locations required for the business transactions, by another means.