canonical: https://jentic.com/apis/papinet.io/order_status # papiNet API Jentic publishes the only available OpenAPI specification for papiNet API, keeping it validated and agent-ready. The papiNet API is a global initiative for the Forest and Paper supply chain, providing standardized endpoints for order status tracking and line item management. It enables supply chain visibility and order management across the paper manufacturing and distribution industry. ## For AI agents Track paper industry orders and line items across 2 endpoints with pagination support. ## Scope Does not handle order creation, invoice generation, or shipment tracking - use for order status and line item retrieval only. ## Capabilities - List all orders with pagination and status filtering - Retrieve detailed order information including line items - Filter orders by status (Active, Cancelled, Completed) - Access order line item quantities and statuses - Navigate paginated results with first, prev, next, last links ## Use cases ### Order Status Tracking Track paper supply chain orders with status filtering and pagination. GET /orders retrieves a paginated list with optional orderStatus filter (Active, Cancelled, Completed), while GET `/orders/{orderId}` returns detailed order information including all line items with quantities and statuses. Example prompt: GET /orders?orderStatus=Active to list active orders, then GET `/orders/{orderId}` for detailed line items ### Supply Chain Line Item Management Access detailed order line item information including quantities, statuses, and changeability flags. Each line item includes quantityContext (Ordered, Confirmed, Shipped, Produced, Invoiced), quantityType (Area, Count, Weight), and quantityValue with UOM (Kilogram, Meter, Ream, etc). Example prompt: GET `/orders/{orderId}` to retrieve all line items with quantities, statuses, and UOM details ### Paginated Order Listing Navigate large order datasets with pagination support. GET /orders returns a ListOfOrders with pagination links (first, prev, next, last) and supports offset and limit query parameters for efficient data retrieval across the supply chain. Example prompt: GET /orders?offset=0&limit=50 to retrieve first page, then follow next link for subsequent pages ### Agent-Driven Supply Chain Tracking via Jentic An AI agent managing paper supply chain operations can track orders, filter by status, and retrieve line item details through Jentic. Jentic resolves intents like 'get active orders' to the right papiNet endpoint and supplies pagination handling. Example prompt: Search Jentic for 'list active orders', load the GET /orders schema with orderStatus filter, and execute ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/orders` | List orders with pagination and status filtering | | GET | `/orders/{orderId}` | Get detailed order with all line items | ## Key resources - **Order** — Order header with status, order number, and line item count - **OrderLineItem** — Line item with quantities, status, and UOM details ## Why Jentic - **Setup:** Wiring the papiNet order-status API by hand means standing up the client against its host, shaping the /orders queries yourself, and handling pagination and retries on your own. Through Jentic you install once, import papiNet from the API Directory, store any production key once, and your agent calls it. - **Permission scoping:** papiNet puts the order id in the URL path (`/orders/{orderId}`), so a rule can pin your agent to one order or to the read-only order lookups. You choose the operations it may call, and since this API only lists and reads orders, it stays limited to retrieval. - **Credential handling:** The papiNet mock server needs no credentials; any production key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'list active orders' or 'get order line items', and Jentic returns the matching papiNet operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **API Order Management** — An order-management API for tracking and updating orders, complementing papiNet's order status and fulfillment workflows. ## FAQ ### Why is there no official OpenAPI spec for papiNet API? While papiNet publishes standards for the paper supply chain, they do not maintain a complete OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call papiNet API via structured tooling. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the papiNet API use? The papiNet API mock server does not require authentication for order status queries. Production implementations may require authentication specific to the paper supplier or distributor. ### What order statuses are supported? papiNet API supports three order statuses: Active (in progress), Cancelled (terminated), and Completed (fulfilled). Use the orderStatus query parameter in GET /orders to filter by status. ### What quantity types are available for line items? Line items support multiple quantity types including Area, Count, GrossWeight, Length, NetWeight, NetNetWeight, NominalWeight, and TareWeight, with corresponding UOMs like Kilogram, Meter, Ream, Piece, SquareMeter, and others specific to the paper industry. ### How does pagination work in the papiNet API? GET /orders returns a ListOfOrders with pagination links (first, prev, next, last) and supports offset and limit query parameters. Use these to navigate large result sets efficiently. ### What is the purpose of quantityContext? quantityContext indicates the stage of the quantity in the order lifecycle: Ordered (customer requested), Confirmed (supplier acknowledged), Shipped (in transit), Produced (manufactured), or Invoiced (billed). This provides supply chain visibility across the fulfillment process. ### Can I limit what my agent is allowed to do with the papiNet API? Yes. Because you run Jentic One yourself, your own rules decide which papiNet operations and credentials the agent may use. This API only lists orders through GET /orders and reads a single order via GET `/orders/{orderId}`, so you can pin the agent to read-only lookups or scope it to a specific order id in the path. It stays limited to retrieval and cannot create orders, generate invoices, or track shipments.