canonical: https://jentic.com/apis/ongoingwarehouse.com/ongoingwarehouse # Ongoingwarehouse Ongoing WMS Goods Owner REST API Jentic publishes the only available OpenAPI specification for Ongoing WMS Goods Owner REST API, keeping it validated and agent-ready. Ongoing WMS is a cloud-based warehouse management system used by third-party logistics providers across the Nordics and Europe. The Goods Owner REST API exposes the operations a brand or merchant needs to integrate Ongoing into an e-commerce stack: managing articles, sending and tracking orders, reading inventory levels, and reconciling invoices. It is the integration surface that brand owners use to talk to a 3PL that runs Ongoing. ## For AI agents Manage product articles, send orders to a 3PL warehouse, and read inventory and shipment movements through a goods owner's account in Ongoing WMS. ## Scope Does not handle storefront, payments, or carrier shipping labels - use for goods owner integration with an Ongoing WMS warehouse only. ## Capabilities - Create and update article master data so the warehouse knows what SKUs to expect - Push customer orders to the warehouse and read back fulfilment status and parcels - Query current inventory per warehouse and historical inventory snapshots - Pull inventory adjustments and stock movements for accounting reconciliation - Retrieve invoices issued by the 3PL to the goods owner - Authenticate with HTTP Basic credentials issued by the warehouse to each goods owner ## Use cases ### E-commerce store to 3PL fulfilment When a Shopify, WooCommerce, or custom storefront receives an order, push it to the Ongoing-powered 3PL via the Goods Owner API so the warehouse can pick, pack, and ship. The same integration reads back parcel and tracking information so the storefront can update the customer. Brands typically wire this up in one to two weeks because the API is a small, focused surface. Example prompt: PUT a new order to `/api/v1/orders` with the customer address, order lines, and goodsOwnerId, then GET `/api/v1/orders/{orderId}` to confirm the warehouse accepted it. ### Multi-warehouse inventory sync Brands that store stock in more than one Ongoing warehouse need a single view of what is available to sell. The Articles inventory endpoints return per-warehouse stock, which an integration can aggregate into a master stock feed for the storefront and the ERP. This prevents overselling and lets ops teams rebalance stock between sites. Example prompt: GET `/api/v1/articles/inventoryPerWarehouse` for goodsOwnerId 123 and return a per-SKU sum of available stock across warehouses. ### Finance reconciliation between 3PL and ERP Finance teams need to match inventory adjustments, stock movements, and 3PL invoices against the ERP each month. The movements, inventoryAdjustments, and invoices endpoints provide the structured source data for this reconciliation, replacing manual CSV exports from the warehouse portal. Most finance integrations are deployed as a nightly batch and take a few days to build. Example prompt: GET `/api/v1/movements` and `/api/v1/invoices` filtered to last month for goodsOwnerId 123 and emit a CSV ready for ERP import. ### AI agent fulfilment operations through Jentic An AI ops agent that monitors fulfilment SLAs can call Ongoing through Jentic without holding the 3PL's basic auth credential. The agent searches Jentic for the order or inventory operation, loads the schema, and queries the warehouse on demand. This pattern is used by ops copilots that triage stuck orders or low-stock alerts across a brand's 3PL network. Example prompt: Search Jentic for 'list ongoing wms orders', load the GET `/api/v1/orders` operation, and execute it filtered to orders not yet shipped after their promise date. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/v1/articles` | List articles for a goods owner | | PUT | `/api/v1/articles` | Create or update an article | | GET | `/api/v1/articles/inventoryPerWarehouse` | Read current stock split by warehouse | | PUT | `/api/v1/orders` | Send a new order to the warehouse | | GET | `/api/v1/orders/{orderId}` | Read the status of a single order | | GET | `/api/v1/movements` | List inbound and outbound stock movements | | GET | `/api/v1/invoices` | List invoices issued by the 3PL | ## Key resources - **Articles** — Product master data: read, update, and inspect inventory per warehouse - **Article Items** — Serialised or batch-tracked article instances - **Orders** — Customer orders sent to the warehouse plus parcel and shipment data - **Inventory Adjustments** — Stock corrections recorded by the warehouse - **Movements** — Inbound and outbound stock movements for audit and reconciliation - **Invoices** — Invoices the 3PL has issued to the goods owner - **Goods Owners** — Account-level information for the goods owner using the warehouse ## Why Jentic - **Setup:** Wiring the Ongoing WMS Goods Owner REST API by hand means setting up HTTP Basic, a long-lived credential with full account scope, and building each article, order, movement, and invoice call against api.ongoingwarehouse.com yourself. Through Jentic you install once, import the Ongoing WMS Goods Owner REST API from the API Directory, store the basic-auth pair once, and your agent calls it. - **Permission scoping:** Ongoing WMS drives most work through collection endpoints for articles, orders, movements, and invoices rather than a resource pinned in the URL path, so you limit the agent to the operations it needs, such as reading inventory per warehouse or fetching an order. Writing articles or sending orders are excluded unless you add those operations to the allowed set. - **Credential handling:** Your Ongoing WMS basic-auth credential 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 'send an order to the warehouse' or 'check stock per warehouse', and Jentic returns the matching Ongoing operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **ShipStation API** — Multi-carrier shipping platform that brands use as an alternative to a full WMS for fulfilment - **Shopify Admin API** — Storefront and order source that pushes orders into Ongoing and reads back fulfilment - **AfterShip API** — Tracking and post-purchase notifications layered on top of warehouse parcel data ## FAQ ### Why is there no official OpenAPI spec for Ongoing WMS Goods Owner REST API? Ongoing publishes its API documentation as HTML at developer.ongoingwarehouse.com but does not ship an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Ongoing via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Ongoing WMS Goods Owner REST API use? The API uses HTTP Basic authentication. Each goods owner is issued a username and password by the 3PL running Ongoing, and those are sent as a standard Authorization header. Through Jentic, the credential is held in the vault and injected at execution time so the agent never sees the password. ### Can I push e-commerce orders to my 3PL warehouse with this API? Yes. Send the order to PUT `/api/v1/orders` with the customer details, order lines, and the goodsOwnerId. You can then read back the order with GET `/api/v1/orders/{orderId}` and PUT to `/api/v1/orders/{orderId}/parcels` to attach parcel data, or DELETE to remove parcels before the order is shipped. ### What are the rate limits for the Ongoing WMS Goods Owner REST API? Ongoing does not publish a single global rate limit in the spec. The platform is multi-tenant and 3PLs configure throttling for their own goods owners, so plan around 429 responses and back off when the warehouse signals it. Bulk reads should use the date and id filters on each endpoint to avoid scanning the whole dataset. ### How do I sync inventory across warehouses through Jentic? Install the SDK with 'pip install jentic', search for the operation with the query 'ongoing wms inventory per warehouse', then load the GET `/api/v1/articles/inventoryPerWarehouse` operation, and execute it for your goodsOwnerId. Jentic handles the basic auth credential and pagination so the agent can build a unified stock view. ### Does this API cover the warehouse-side of Ongoing WMS? No. This is the Goods Owner REST API, used by brands and merchants whose stock sits in an Ongoing warehouse. Operations such as configuring warehouse layouts, picking lists, and 3PL administration sit in a separate API surface and are not exposed here. ### Can I limit what my agent is allowed to do with the Ongoing WMS Goods Owner REST API? Yes. Because you run Jentic One yourself, your own rules decide which Ongoing operations and credentials the agent may use. Since Ongoing works through collection endpoints for articles, orders, movements, and invoices rather than a fixed resource in the URL, you can allow only the calls the agent needs, such as GET `/api/v1/articles/inventoryPerWarehouse` to read stock or GET `/api/v1/orders/{orderId}` to check an order. Write operations like PUT `/api/v1/orders` to send an order or PUT `/api/v1/articles` to update a SKU stay blocked until you add them to the allowed set.