Can AI agents automate Ongoing WMS?

Ongoing WMS is automatable today through its goods-owner REST API. This record is Ongoing WMS, the cloud warehouse system from Ongoing Warehouse AB. It is not nShift or Centra. The developer guidelines say an ERP or ecommerce system can create articles, purchase orders, and orders, then poll for received and sent status. REST paths named on that page include /api/v1/purchaseOrders and /api/v1/orders. SOAP equivalents are ProcessInOrder and ProcessOrder. API access is a username and password created under Administration, API for goods owners. The username must start with WSI, and one API user belongs to one goods owner. Invoice endpoints are blocked unless that user is allowed to see invoicing information. The automation API is a separate user that can see every goods owner. Webhooks POST JSON when an event such as an order pick occurs. Retry policies and basic, fixed-token, or mTLS authentication toward the receiver are documented. The guidelines say polling every 15 minutes is enough for the common status checks. No vendor page was opened that settles whether Ongoing publishes an MCP server. https://developer.ongoingwarehouse.com/llms.txt returned an HTML page. A supported CLI and connector catalogs were not opened. Computer-use viability is unassessed. The API scores 7 and is the best path.

Best path today: api · Overall automatability: 7/10