Logiwa Integration API

The Logiwa Integration API is an RPC-over-HTTP interface with 81 documented operations covering products and kits, shipment orders and order details, purchase orders, receipt orders and receiving, inventory reporting and adjustment, available-to-promise, locations and pallets, count plans, documents, warehouse tasks and productivity, transaction history, and 3PL contract billing. Every operation is a POST that carries its filters in the JSON body; there are no path or query parameters. Outcome is signalled by a Success boolean in the response body rather than by HTTP status codes.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/logiwa-integration-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑
name: Logiwa Integration API
description: The Logiwa Integration API is an RPC-over-HTTP interface with 81 documented operations covering
  products and kits, shipment orders and order details, purchase orders, receipt orders and receiving,
  inventory reporting and adjustment, available-to-promise, locations and pallets, count plans, documents,
  warehouse tasks and productivity, transaction history, and 3PL contract billing. Every operation is
  a POST that carries its filters in the JSON body; there are no path or query parameters. Outcome is
  signalled by a Success boolean in the response body rather than by HTTP status codes.
humanURL: https://developer.logiwa.com/
baseURL: https://app.logiwa.com/en/api/IntegrationApi
tags:
- Warehouse Management
- Fulfillment
- Inventory Management
- Order Management
- Logistics
properties:
- type: Documentation
  url: https://developer.logiwa.com/?id=5df0d8bfe6466c2eec992f31
- type: APIReference
  url: https://developer.logiwa.com/
- type: GettingStarted
  url: https://developer.logiwa.com/?id=5df0d8bfe6466c2eec992f31
- type: Authentication
  url: authentication/logiwa-authentication.yml
- type: OAuthScopes
  url: scopes/logiwa-scopes.yml
- type: Conventions
  url: conventions/logiwa-conventions.yml
- type: ErrorCatalog
  url: errors/logiwa-error-codes.yml
- type: RateLimits
  url: rate-limits/logiwa-rate-limits.yml
- type: DataModel
  url: data-model/logiwa-data-model.yml
- type: Conformance
  url: conformance/logiwa-conformance.yml
- type: Lifecycle
  url: lifecycle/logiwa-lifecycle.yml
x-base-url-note: The API host is per-tenant. The documented pattern is https://{environment}.logiwa.com
  with the Integration API mounted at /en/api/IntegrationApi, and the matching token host at https://{environment}api.logiwa.com/token.
  app.logiwa.com (paired with appapi.logiwa.com) and wms.logiwa.com (paired with wmsapi.logiwa.com) are
  the two environments Logiwa names in its own Login documentation; app.logiwa.com is recorded here as
  the concrete production base and was confirmed live on 2026-08-25 (POST /en/api/IntegrationApi/LookUp
  returned HTTP 401 with the documented authorization envelope).