How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Logiless Articles API

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

Logiless Articles API is one of 9 APIs that Logiless publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Articles. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 6 operations across 6 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://app2.logiless.com/api/v1.

6 operations 6 paths 1 schemas 1 DELETE2 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://app2.logiless.com/api/v1
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Logiless Articles API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow. By default, every request must be authenticated.

  • oauth2 — OAuth 2.0 authorization-code flow. Applications must be registered and reviewed (3–5 business days) in the LOGILESS Developers console. Access and refresh toke…

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Articles 6

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

GET
/merchant/{merchant_id}/articles
List articles / product master (商品マスタの一覧を取得)
listArticles 3 params → 200
POST
/merchant/{merchant_id}/articles/new
Create an article
createArticle 1 param body → 200
POST
/merchant/{merchant_id}/articles/new/multiple
Create multiple articles
createArticlesMultiple 1 param body → 200
PUT
/merchant/{merchant_id}/articles/{id}
Update an article
updateArticle 2 params body → 200
DELETE
/merchant/{merchant_id}/articles/{id}/delete
Delete an article
deleteArticle 2 params → 200
GET
/merchant/{merchant_id}/article_maps
List article maps (商品対応表の一覧を取得)
listArticleMaps 3 params → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Article (4 properties). Each schema is shown below with its type and property counts.

Article
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

logiless-articles-api-openapi.yml Raw ↑

Other APIs Logiless publishes across the network.

Logiless Inbound Deliveries API
Logiless Inter-Warehouse Transfers API
Logiless Inventory API
Logiless Locations API
Logiless Outbound Deliveries API
Logiless Sales Orders API
Logiless Sales Returns API
Logiless Suppliers API
Where this information came from

This is an independent, third-party profile of Logiless Articles API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.