Logiwa is a Chicago-based cloud fulfillment software company whose flagship product, Logiwa IO, is a warehouse management and fulfillment management system (WMS/FMS) built for high-volume B2C and DTC brands, wholesalers and third-party logistics providers (3PLs). Logiwa exposes a documented Integration API covering products, shipment orders, purchase orders, receipt orders, inventory, locations, count plans, documents, warehouse tasks, transaction history and 3PL billing, plus an eleven-topic webhook surface for order, inventory, movement and shipment tracking events. The API is an RPC-over-POST design: 81 documented operations, all reached by POST to /en/api/IntegrationApi/{Method} on a per-tenant host, authenticated with an OAuth 2.0 password grant that yields a bearer token. Logiwa publishes no OpenAPI, AsyncAPI or other machine-readable contract, and no first-party SDKs; the reference is a JavaScript-rendered developer portal and API credentials are provisioned by sales rather than self-service.
Logiwa is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Warehouse Management, Fulfillment, Logistics, and Supply Chain.
The Logiwa catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Logiwa’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, pricing, authentication, and 20 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/logiwa/"><img src="https://apis.io/badge/logiwa/card.svg" alt="Logiwa on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
MCP Server+12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples+7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
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 or...
aid: logiwa
name: Logiwa
description: 'Logiwa is a Chicago-based cloud fulfillment software company whose flagship product, Logiwa IO, is a warehouse
management and fulfillment management system (WMS/FMS) built for high-volume B2C and DTC brands, wholesalers and third-party
logistics providers (3PLs). Logiwa exposes a documented Integration API covering products, shipment orders, purchase orders,
receipt orders, inventory, locations, count plans, documents, warehouse tasks, transaction history and 3PL billing, plus
an eleven-topic webhook surface for order, inventory, movement and shipment tracking events. The API is an RPC-over-POST
design: 81 documented operations, all reached by POST to /en/api/IntegrationApi/{Method} on a per-tenant host, authenticated
with an OAuth 2.0 password grant that yields a bearer token. Logiwa publishes no OpenAPI, AsyncAPI or other machine-readable
contract, and no first-party SDKs; the reference is a JavaScript-rendered developer portal and API credentials are provisioned
by sales rather than self-service.'
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: false
label: Hosted service · you call their endpoint
confidence: medium
source:
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: unknown
onboarding: unknown
trial: false
try_now: false
public: false
label: Unknown
confidence: low
source:
- authentication
- scopes
- rate-limits
- security
generated: '2026-11-06'
method: derived
image: https://developer.logiwa.com/Content/img/logiwa_new_logo.png
url: https://raw.githubusercontent.com/api-evangelist/logiwa/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-25'
modified: '2026-10-06'
tags:
- Company
- Warehouse Management
- Fulfillment
- Logistics
- Supply Chain
- Inventory
- Order Management
- Third Party Logistics
- E-Commerce
- Shipping
- Webhook
- Software-as-a-Service
tags_raw:
- Company
- Warehouse Management
- Fulfillment
- Logistics
- Supply Chain
- Inventory Management
- Order Management
- Third Party Logistics
- Ecommerce
- Shipping
- Webhooks
- SaaS
apis:
- 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
- Order Management
- Logistics
tags_raw:
- 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).
- name: Logiwa Webhooks
description: Logiwa's outbound event surface. Eleven documented topics deliver order status, receipt and purchase order
status, inventory change, location update, movement, receipt, shipment tracking and consolidated shipment events to a
customer-configured callback URL. Subscriptions are configured in the Logiwa WMS UI, not through the API. Logiwa states
delivery is not guaranteed and ordering is not guaranteed across topics, and publishes no callback signing mechanism.
humanURL: https://developer.logiwa.com/?id=633d97bae6466c1730066501
baseURL: https://developer.logiwa.com/?id=633d97bae6466c1730066501
tags:
- Webhook
- Event
- Fulfillment
tags_raw:
- Webhooks
- Events
- Fulfillment
properties:
- type: Webhooks
url: asyncapi/logiwa-webhooks.yml
- type: Documentation
url: https://developer.logiwa.com/?id=633d97bae6466c1730066501
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- url: https://www.logiwa.com/blog/feed
type: BlogRSS
- type: Website
url: https://www.logiwa.com/
- type: DeveloperPortal
url: https://developer.logiwa.com/
- 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: Blog
url: https://www.logiwa.com/blog
- type: Support
url: https://www.logiwa.com/contact-us
- type: Pricing
url: https://www.logiwa.com/pricing
- type: PrivacyPolicy
url: https://www.logiwa.com/privacy-policy
- 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: Plans
url: plans/logiwa-plans-pricing.yml
- type: Lifecycle
url: lifecycle/logiwa-lifecycle.yml
- type: Conformance
url: conformance/logiwa-conformance.yml
- type: Compliance
url: security/logiwa-trust-center.yml
- type: TrustCenter
url: security/logiwa-trust-center.yml
- type: DomainSecurity
url: security/logiwa-domain-security.yml
- type: DataModel
url: data-model/logiwa-data-model.yml
- type: Packages
url: packages/logiwa-packages.yml
- type: Webhooks
url: asyncapi/logiwa-webhooks.yml
- type: WellKnown
url: well-known/logiwa-well-known.yml
- type: LLMsTxt
url: llms/logiwa-llms.txt
- type: AgentSkill
url: skills/_index.yml
x-enrichment:
date: '2026-08-25'
status: enriched
artifacts_added: 24
pass: local-v1
x-contract:
machine_readable_spec: false
detail: Logiwa publishes 81 fully documented operations plus 11 webhook topics at https://developer.logiwa.com/, but no
OpenAPI, Swagger, AsyncAPI, GraphQL SDL, WSDL or .proto. Probed 12 spec paths across 7 hosts on 2026-08-25 — docs host
404s, application hosts 302 to login, API gateway hosts blanket-401. See openapi/README.md for the full probe table.
docs_readable: true
docs_note: The developer portal is an AngularJS SPA whose content is served by two of Logiwa's own public POST endpoints
(/api/Menu/GetMenuList and /api/EndPointApi/GetEndPointDetail). All derived artifacts in this repository were read from
that anonymous public surface.
Logiwa API — frequently asked questions
Does Logiwa have an API?
Yes. APIs.io lists 2 APIs from Logiwa, including Logiwa Integration API and Logiwa Webhooks.
How do I authenticate with the Logiwa API?
Logiwa documents its authentication (2 schemes). The details are profiled on APIs.io as Logiwa Authentication.
Is the Logiwa API ready for AI agents?
Logiwa has a Kin Score of 46.6 out of 100 (developing) and an Agent Readiness score of 34.4 (agent-ready), scored by API Evangelist on 2026-11-06.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: