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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Invendor

Invendor WMSLocations API

The WMSLocations API from Invendor — 9 operation(s) for wmslocations.

Documentation Provider Profile APIs.io OpenAPI GitHub

Invendor WMSLocations API is one of 42 APIs that Invendor publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include WMSLocations. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 14 operations across 9 paths, and defines 19 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against the base URL https://api.invendor.com.

14 operations 9 paths 19 schemas 2 DELETE4 GET7 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.invendor.com
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Invendor WMSLocations API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 1 scope. By default, every request must be authenticated.

Paths & Operations 14

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

WMSLocations 14
GET
/v1/WMSLocations/{locationId}/areas
Get all location areas
getV1WMSLocationsByLocationIdAreas 2 params → 200401403
POST
/v1/WMSLocations/{locationId}/areas
Create new area for location. (All the lockers etc must be defined as areas)
postV1WMSLocationsByLocationIdAreas 2 params body → 201400401403
GET
/v1/WMSLocations/{locationId}/areas/{areaId}
Get location area details
getV1WMSLocationsByLocationIdAreasByAreaId 3 params → 200401403
PUT
/v1/WMSLocations/{locationId}/areas/{areaId}
Update WMSArea
putV1WMSLocationsByLocationIdAreasByAreaId 3 params body → 200400401403
DELETE
/v1/WMSLocations/{locationId}/areas/{areaId}
Delete an selected area
deleteV1WMSLocationsByLocationIdAreasByAreaId 3 params → 200400401403
POST
/v1/WMSLocations/areas/cabinet/attach
Attach WMS location to cabinet
AttachWMSLocationToCabinet 1 param body → 200400401403
GET
/v1/WMSLocations/{locationId}/addresses
Get location wms addresses
getV1WMSLocationsByLocationIdAddresses 12 params → 200400401403
POST
/v1/WMSLocations/{locationId}/addresses
Create new wh address for area
postV1WMSLocationsByLocationIdAddresses 2 params body → 201400401403
POST
/v1/WMSLocations/{locationId}/addresses/bulk
Bulk insert of wh address for area
postV1WMSLocationsByLocationIdAddressesBulk 2 params body → 200400401403
DELETE
/v1/WMSLocations/{locationId}/addresses/{wmsLocationId}
Delete wh address in a location by address
deleteV1WMSLocationsByLocationIdAddressesByWmsLocationId 3 params → 200400401403
POST
/v1/WMSLocations/{locationId}/addresses/generate
Generate wh aadresses on predefined parameters
postV1WMSLocationsByLocationIdAddressesGenerate 2 params body → 200400401403
POST
/v1/WMSLocations/{locationId}/addresses/delete
Delete selected or all wh aadresses in a location
postV1WMSLocationsByLocationIdAddressesDelete 2 params body → 200400401403
GET
/v1/WMSLocations/validate
Validates whether a single WMS location ID exists for a given location
getV1WMSLocationsValidate 3 params → 200400401403
POST
/v1/WMSLocations/validate
Validates multiple WMS location IDs for a given location.
postV1WMSLocationsValidate 1 param body → 200400401403

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are CabinetLocationItemsParam (11 properties), WMSLocationResponse (8 properties), BinItem (8 properties), GenerateWMSLocationsRequest (6 properties). Each schema is shown below with its type and property counts.

AttachWmsLocationToCabinetRequest
object
2 properties
CreateWMSAreaRequest
object
4 properties
WMSAreaType
integer
Int32ResourceCreatedResponse
object
1 property
WMSLocationResponse
object
8 properties
Error
object
2 properties
WeightType
integer
ShelfBinValueTuple
object
BulkDeleteWMSLocationsRequest
object
3 properties
UpdateWMSAreaRequest
object
3 properties
CreateAreaWMSLocationRequest
object
5 properties
ApiErrorResponse
object
1 property
GenerateWMSLocationsRequest
object
6 properties
Compartment
object
3 properties
Shelf
object
4 properties
Bin
object
4 properties
CabinetLocationItemsParam
object
11 properties
BinItem
object
8 properties
ValidateWmsLocationIdsRequest
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

invendor-wmslocations-api-openapi.yml Raw ↑

Other APIs Invendor publishes across the network.

Invendor Accounts API
AE Profile APIs.io
Invendor Auth API
AE Profile APIs.io
Invendor Barcodes API
AE Profile APIs.io
Invendor Consumption API
AE Profile APIs.io
Invendor Devices API
AE Profile APIs.io
Invendor Dimensions API
AE Profile APIs.io
Invendor DimensionValues API
AE Profile APIs.io
Invendor Doors API
AE Profile APIs.io
Invendor DynamicScanContent API
AE Profile APIs.io
Invendor ExtendedProperties API
AE Profile APIs.io
Invendor FlagTypes API
AE Profile APIs.io
Invendor Gravity API
AE Profile APIs.io
#WMSLocations
← Back to I APIs
API Details
ID
invendor:invendor-wmslocations-api
Base URL
https://api.invendor.com
Docs
https://api.invendor.com/swagger/index.html
Provider
Invendor
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=invendor-wmslocations-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/invendor-wmslocations-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of Invendor WMSLocations 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.