Logiless

LOGILESS (ロジレス) is a Japanese cloud EC logistics platform that unifies order management (OMS) and warehouse management (WMS) for e-commerce merchants — automating order intake from marketplaces and shopping carts (Rakuten, Shopify, ColorMe, futureshop, ec-force and more), inventory synchronization, allocation, shipping-label issuance and warehouse operations. LOGILESS exposes a RESTful, OAuth2-protected API (scoped per merchant) for reading and writing sales orders, outbound and inbound deliveries, sales returns, inter-warehouse transfers, articles (product master), multi-layer inventory summaries, warehouses, stores and suppliers. The company is a 500 Global portfolio company. This profile was enriched by the API Evangelist pipeline from LOGILESS's public developer documentation; the OpenAPI here is derived and not an official LOGILESS artifact.

Logiless publishes 9 APIs on the APIs.io network, including Articles API, Inbound Deliveries API, Inter-Warehouse Transfers API, and 6 more. Tagged areas include Logistics, E-Commerce, Order Management, Warehouse Management, and Inventory.

Logiless’ developer surface includes authentication, changelog, documentation, API reference, getting-started guide, support, engineering blog, and 21 more developer resources.

🌐 Visit website 📡 Source on GitHub

38.4/100 thin ▬ flat Agent 31/100 agent ready Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-09-25 · rubric v0.23.0

AccessSelf serve

1 APIs

Logistics E-Commerce Order Management Warehouse Management Inventory Fulfillment Shipping OMS WMS Japan

Kin Score

Kin Score How this is scored →
scored 2026-09-25 · rubric v0.23.0

Composite quality — 38.4/100 · thin

Contract Quality 2.2 / 19

Developer Ergonomics 8.8 / 15

Access Clarity 6.7 / 15

Operational Transparency 3.6 / 10

Contract Governance 0.4 / 9

Discoverability 5.5 / 8

Regulatory Posture 5.1 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 31/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/logiless: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 9

Individual APIs this provider publishes, each with its own machine-readable definition.

Logiless Articles API

商品マスタ / 商品対応表 — product master and mapping

Logiless Inbound Deliveries API

入荷予定伝票 — expected inbound shipments

Logiless Inter-Warehouse Transfers API

倉庫間移動伝票 — stock transfers between warehouses

Logiless Inventory API

在庫 / 保管状況 / 日次在庫表 / 在庫操作ログ / 倉庫別発注点 — inventory & storage summaries

Logiless Locations API

店舗 / 倉庫 / ロケーション — stores, warehouses and locations

Logiless Outbound Deliveries API

出荷伝票 — shipment records

Logiless Sales Orders API

受注伝票 — order intake, editing, confirmation and reversal

Logiless Sales Returns API

売上返品 — returns

Logiless Suppliers API

仕入先マスタ — supplier master

Scroll for all 9

Open Collections 10

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

LOGILESS Articles API

OPEN COLLECTION

LOGILESS Articles Inbound Deliveries API

OPEN COLLECTION

LOGILESS Articles Inter-Warehouse Transfers API

OPEN COLLECTION

LOGILESS Articles Inventory API

OPEN COLLECTION

LOGILESS Articles Locations API

OPEN COLLECTION

LOGILESS Articles Outbound Deliveries API

OPEN COLLECTION

LOGILESS Articles Sales Orders API

OPEN COLLECTION

LOGILESS Articles Sales Returns API

OPEN COLLECTION

LOGILESS Articles Suppliers API

OPEN COLLECTION

Scroll for all 10

Rate Limits 1

Documented rate limits and quota policies.

Logiless Rate Limits

1 limits

RATE LIMITS

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Logiless Authentication

oauth2 · 1 scheme

SECURITY

Logiless Domain Security

TLSv1.2 · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Logiless Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Login

Documentation 3

Reference material describing how the API behaves

OpenAPI

OpenAPI

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

DataModel

Conformance

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

OAuthScopes

OAuthScopes

DomainSecurity

DomainSecurity

Operate 4

Status, limits, changes, and where to get help

RateLimits

ChangeLog

Support

Contact

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Blog

Blog

Website

Website

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: logiless
name: Logiless
description: LOGILESS (ロジレス) is a Japanese cloud EC logistics platform that unifies order management (OMS) and warehouse management
  (WMS) for e-commerce merchants — automating order intake from marketplaces and shopping carts (Rakuten, Shopify, ColorMe,
  futureshop, ec-force and more), inventory synchronization, allocation, shipping-label issuance and warehouse operations.
  LOGILESS exposes a RESTful, OAuth2-protected API (scoped per merchant) for reading and writing sales orders, outbound and
  inbound deliveries, sales returns, inter-warehouse transfers, articles (product master), multi-layer inventory summaries,
  warehouses, stores and suppliers. The company is a 500 Global portfolio company. This profile was enriched by the API Evangelist
  pipeline from LOGILESS's public developer documentation; the OpenAPI here is derived and not an official LOGILESS artifact.
url: https://raw.githubusercontent.com/api-evangelist/logiless/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://support.logiless.com/wp-content/uploads/2021/06/ogp.png
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
x-tier: profiled
x-tier-reason: enriched-from-developer-docs
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Logistics
- E-Commerce
- Order Management
- Warehouse Management
- Inventory
- Fulfillment
- Shipping
- OMS
- WMS
- Japan
tags_raw:
- Logistics
- E-commerce
- Order Management
- Warehouse Management
- Inventory
- Fulfillment
- Shipping
- OMS
- WMS
- Japan
apis:
- aid: logiless:logiless-articles-api
  name: Logiless Articles API
  description: 商品マスタ / 商品対応表 — product master and mapping
  humanURL: https://app2.logiless.com/developer/
  baseURL: https://app2.logiless.com/api/v1
  tags:
  - Articles
  properties:
  - type: OpenAPI
    url: openapi/logiless-articles-api-openapi.yml
  - type: Documentation
    url: https://app2.logiless.com/developer/
  - type: APIReference
    url: https://app2.logiless.com/developer/documents/specifications
  - type: Authentication
    url: https://app2.logiless.com/developer/documents/authentication
- aid: logiless:logiless-inbound-deliveries-api
  name: Logiless Inbound Deliveries API
  description: 入荷予定伝票 — expected inbound shipments
  humanURL: https://app2.logiless.com/developer/
  baseURL: https://app2.logiless.com/api/v1
  tags:
  - Inbound Deliveries
  properties:
  - type: OpenAPI
    url: openapi/logiless-inbound-deliveries-api-openapi.yml
  - type: Documentation
    url: https://app2.logiless.com/developer/
  - type: APIReference
    url: https://app2.logiless.com/developer/documents/specifications
  - type: Authentication
    url: https://app2.logiless.com/developer/documents/authentication
- aid: logiless:logiless-inter-warehouse-transfers-api
  name: Logiless Inter-Warehouse Transfers API
  description: 倉庫間移動伝票 — stock transfers between warehouses
  humanURL: https://app2.logiless.com/developer/
  baseURL: https://app2.logiless.com/api/v1
  tags:
  - Inter-Warehouse Transfers
  properties:
  - type: OpenAPI
    url: openapi/logiless-inter-warehouse-transfers-api-openapi.yml
  - type: Documentation
    url: https://app2.logiless.com/developer/
  - type: APIReference
    url: https://app2.logiless.com/developer/documents/specifications
  - type: Authentication
    url: https://app2.logiless.com/developer/documents/authentication
- aid: logiless:logiless-inventory-api
  name: Logiless Inventory API
  description: 在庫 / 保管状況 / 日次在庫表 / 在庫操作ログ / 倉庫別発注点 — inventory & storage summaries
  humanURL: https://app2.logiless.com/developer/
  baseURL: https://app2.logiless.com/api/v1
  tags:
  - Inventory
  properties:
  - type: OpenAPI
    url: openapi/logiless-inventory-api-openapi.yml
  - type: Documentation
    url: https://app2.logiless.com/developer/
  - type: APIReference
    url: https://app2.logiless.com/developer/documents/specifications
  - type: Authentication
    url: https://app2.logiless.com/developer/documents/authentication
- aid: logiless:logiless-locations-api
  name: Logiless Locations API
  description: 店舗 / 倉庫 / ロケーション — stores, warehouses and locations
  humanURL: https://app2.logiless.com/developer/
  baseURL: https://app2.logiless.com/api/v1
  tags:
  - Location
  tags_raw:
  - Locations
  properties:
  - type: OpenAPI
    url: openapi/logiless-locations-api-openapi.yml
  - type: Documentation
    url: https://app2.logiless.com/developer/
  - type: APIReference
    url: https://app2.logiless.com/developer/documents/specifications
  - type: Authentication
    url: https://app2.logiless.com/developer/documents/authentication
- aid: logiless:logiless-outbound-deliveries-api
  name: Logiless Outbound Deliveries API
  description: 出荷伝票 — shipment records
  humanURL: https://app2.logiless.com/developer/
  baseURL: https://app2.logiless.com/api/v1
  tags:
  - Outbound Deliveries
  properties:
  - type: OpenAPI
    url: openapi/logiless-outbound-deliveries-api-openapi.yml
  - type: Documentation
    url: https://app2.logiless.com/developer/
  - type: APIReference
    url: https://app2.logiless.com/developer/documents/specifications
  - type: Authentication
    url: https://app2.logiless.com/developer/documents/authentication
- aid: logiless:logiless-sales-orders-api
  name: Logiless Sales Orders API
  description: 受注伝票 — order intake, editing, confirmation and reversal
  humanURL: https://app2.logiless.com/developer/
  baseURL: https://app2.logiless.com/api/v1
  tags:
  - Sales Orders
  properties:
  - type: OpenAPI
    url: openapi/logiless-sales-orders-api-openapi.yml
  - type: Documentation
    url: https://app2.logiless.com/developer/
  - type: APIReference
    url: https://app2.logiless.com/developer/documents/specifications
  - type: Authentication
    url: https://app2.logiless.com/developer/documents/authentication
- aid: logiless:logiless-sales-returns-api
  name: Logiless Sales Returns API
  description: 売上返品 — returns
  humanURL: https://app2.logiless.com/developer/
  baseURL: https://app2.logiless.com/api/v1
  tags:
  - Sales Returns
  properties:
  - type: OpenAPI
    url: openapi/logiless-sales-returns-api-openapi.yml
  - type: Documentation
    url: https://app2.logiless.com/developer/
  - type: APIReference
    url: https://app2.logiless.com/developer/documents/specifications
  - type: Authentication
    url: https://app2.logiless.com/developer/documents/authentication
- aid: logiless:logiless-suppliers-api
  name: Logiless Suppliers API
  description: 仕入先マスタ — supplier master
  humanURL: https://app2.logiless.com/developer/
  baseURL: https://app2.logiless.com/api/v1
  tags:
  - Suppliers
  properties:
  - type: OpenAPI
    url: openapi/logiless-suppliers-api-openapi.yml
  - type: Documentation
    url: https://app2.logiless.com/developer/
  - type: APIReference
    url: https://app2.logiless.com/developer/documents/specifications
  - type: Authentication
    url: https://app2.logiless.com/developer/documents/authentication
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Overlay
  url: overlays/logiless-overlay.yaml
- type: OpenAPI
  url: openapi/_original/logiless-openapi.yml
- type: Authentication
  url: authentication/logiless-authentication.yml
- type: OAuthScopes
  url: scopes/logiless-scopes.yml
- type: Conventions
  url: conventions/logiless-conventions.yml
- type: ErrorCatalog
  url: errors/logiless-problem-types.yml
- type: RateLimits
  url: rate-limits/logiless-rate-limits.yml
- type: Lifecycle
  url: lifecycle/logiless-lifecycle.yml
- type: ChangeLog
  url: changelog/logiless-changelog.yml
- type: DataModel
  url: data-model/logiless-data-model.yml
- type: Conformance
  url: conformance/logiless-conformance.yml
- type: X-MCPServerCandidate
  url: mcp/logiless-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/logiless-llms.txt
- type: AgentSkill
  url: skills/_index.yml
- type: DomainSecurity
  url: security/logiless-domain-security.yml
- type: DeveloperPortal
  url: https://app2.logiless.com/developer/
- type: Documentation
  url: https://support.logiless.com/
- type: APIReference
  url: https://app2.logiless.com/developer/documents/specifications
- type: GettingStarted
  url: https://app2.logiless.com/developer/documents/authentication
- type: Support
  url: https://support.logiless.com/
- type: Blog
  url: https://www.logiless.com/blog/
- type: Pricing
  url: https://www.logiless.com/price/
- type: SignUp
  url: https://app2.logiless.com/merchant/sign_up
- type: Login
  url: https://app2.logiless.com/merchant/sign_in
- type: TermsOfService
  url: https://www.logiless.com/legal/terms/
- type: PrivacyPolicy
  url: https://www.logiless.com/legal/privacy-policy/
- type: Contact
  url: https://go.logiless.com/contact
- type: Website
  url: https://www.logiless.com
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 19
  pass: local-v1

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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 provider

curl "https://apis.io/api/v1/providers/logiless"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/logiless/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/logiless/evidence"

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

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.

GitHub Google LinkedIn

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