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.

papiNet API 2.0.0 Released!

The papiNet Central Work Group is pleased to announce the official release of the papiNet API 2.0.0! As announced, this release contains a significant redesign of the papiNet API focusing on the Purchase Order use case.

Changelog

Deletion

• GET /orders
• GET /orders/{orderId}
• GET /shipments/{shipmentId}
• GET /seller-products
• GET /seller-products/{sellerProductId}
• POST /customer-articles
• PUT /customer-articles/{customerArticleId}
• PATCH /customer-articles/{customerArticleId}
• DELETE /customer-articles/{customerArticleId}
• POST /seller-products/{sellerProductId}/check-availability
• POST /customer-articles/{customerArticleId}/check-availability

Updates

• GET /customer-articles
• GET /customer-articles/{customerArticleId}
• GET /locations/{locationId}

Additions

• GET /locations
• GET /parties
• GET /parties/{partyId}
• 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 seller has already defined the necessary customer-articles, parties, and locations required for the business transactions, by another means than papiNet API.

It should be noted that, for now, this simplified operational structure excludes the step of defining customer-articles from seller-products, which is assumed to have already been completed by the seller prior to the start of the business transactions. In addition to that, our assumption is that each property of the customer-article has only one value, but this restriction will change in the future.

Our initial approach will also be to start with a simplified operational structure in which the purchase-order is limited to direct delivery to the shipToLocation.

Important Notes

This version 2.0.0 of the papiNet API mainly contains incompatible changes from version 1.3.0. However, the "Order Status Use Case" will be soon re-incorporated within a version 2.1.0 using a dedicated new API endpoint.

papiNet API 1.3.0 Released!

The papiNet Central Work Group is pleased to announce the official release of the papiNet API 1.3.0! This release contains 3 new API endpoints that support our new Availability use case.

Changelog

Additions

• Add the following 3 API endpoints to support Availability use case:

  • POST /seller-products/{sellerProductId}/check-availability
  • POST /customer-articles/{customerArticleId}/check-availability
  • GET /locations/{locationId}

• Add the Availability use case

Updates

• Provide a new papiNet mock based on Pact to handle the simulation of the Availability use case

Clarifications

• None

Important Notes

For the next release, we are planning to fundamentally review some of our concepts. It will result in incompatible changes that will result in an increment of our major version (2.0.0).

papiNet API 1.2.0 Released!

The papiNet Central Working Group is pleased to announce the official release of the papiNet API 1.2.0! This release contains 8 new API endpoints to manage the /seller-products and customer-articles resources that support our new Catalogue use case.

Changelog

Additions

• Add the following 8 API endpoint to support Catalog use case:

  • GET /seller-products
  • GET /seller-products/{sellerProductId}
  • POST /customer-articles
  • PUT /customer-articles/{customerArticleId}
  • PATCH /customer-articles/{customerArticleId}
  • GET /customer-articles
  • GET /customer-articles/{customerArticleId}
  • DELETE /customer-articles/{customerArticleId}

• Add the Catalogue use case

Updates

• Update the papiNet mock to handle the simulation of the Catalogue use case

Clarifications

• Minor reviews within the Order Status and Shipment use cases

papiNet API 1.1.0 Released!

The papiNet Central Working Group is pleased to announce the official release of the papiNet API 1.1.0!

Changelog

Additions

• Add the GET /shipments and GET /shipments/{shipmentId} API endpoints to manage shipments
• Add the Shipment Status use case

Updates

• Update the papiNet mock to handle the simulation of the Shipment Status use case

Clarifications

• Minor reviews within the Order Status use case