Skip to content

papiNet API 2.0.0 Released!

Choose a tag to compare

View all tags
@patricekrakow patricekrakow released this 11 Oct 11:55
· 273 commits to master since this release
2.0.0
0da64f6
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

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.

Assets 2
Loading