Ongoing WMS Goods Owner REST API

Name: Ongoing WMS Goods Owner REST API API
Brand: Ongoing WMS Goods Owner REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceInventorybasic16 EndpointsREST

For 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.

Connect the Ongoing WMS Goods Owner REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ongoing WMS Goods Owner REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Ongoing WMS Goods Owner REST API API.

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

GET STARTED

Start building with Ongoing WMS Goods Owner REST API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Ongoing WMS Goods Owner REST API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Ongoing WMS Goods Owner REST API API for, with concrete tasks.

★ 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.

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.

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.

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.

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

16 endpoints — jentic publishes the only available openapi specification for ongoing wms goods owner rest api, keeping it validated and agent-ready.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Ongoing WMS uses HTTP Basic auth, which is a long-lived credential with full account scope. Storing it in the Jentic vault and injecting it at execution time prevents the credential from leaking through agent prompts, logs, or chat transcripts.

Intent-based discovery

Agents search Jentic with intents like 'send order to warehouse' or 'check stock per warehouse' and Jentic returns the matching Ongoing operations with their input schemas, removing the need to read the developer.ongoingwarehouse.com docs.

Time to first call

Direct Ongoing integration: 1-2 weeks for order push, inventory sync, basic auth handling, and pagination. Through Jentic: under 1 hour to search, load the schema, and execute the first call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

ShipStation API

Multi-carrier shipping platform that brands use as an alternative to a full WMS for fulfilment

Choose ShipStation when the brand ships from its own warehouse and wants a label and rates layer rather than handing fulfilment to a 3PL on Ongoing.

Complementary

Shopify Admin API

Storefront and order source that pushes orders into Ongoing and reads back fulfilment

Use Shopify alongside Ongoing when the storefront is on Shopify and the brand wants the order, fulfilment, and inventory loops connected end-to-end.

Complementary

AfterShip API

Tracking and post-purchase notifications layered on top of warehouse parcel data

Use AfterShip downstream of Ongoing when the brand wants branded tracking pages and proactive delivery exception alerts for the customer.

FAQs

Specific to using Ongoing WMS Goods Owner REST API API through Jentic.

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 at https://app.jentic.com/sign-up.

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.