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

MODIVO Inventory In Store Pickup API Get Pickup Locations V1 API

Get Pickup Locations filtered by provided Search Request. Pickup Location entities are Immutable object and can not be changed after creation. All modification of Pickup Location must be done through @see \Magento\InventoryApi\Api\SourceRepositoryInterface

MODIVO Inventory In Store Pickup API Get Pickup Locations V1 API is one of 37 APIs that MODIVO publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include inventoryInStorePickupApiGetPickupLocationsV1. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, authentication docs, and rate-limit docs.

This API exposes 1 operation across 1 path, and defines 16 schemas. It is described by OpenAPI 3.2.0, at version 2.4.

Requests are made against a single base URL, https://modivo.pl/rest/all.

1 operations 1 paths 16 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.4
Base URL
https://modivo.pl/rest/all
Authentication
API Key
Resource Areas
1

Authentication & Security 1

MODIVO Inventory In Store Pickup API Get Pickup Locations V1 API declares 1 security scheme for authenticating requests. An API key is passed in the header as api_key (api_key).

  • api_key — Magento integration/customer bearer token supplied in the Authorization header (Bearer ).

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

inventoryInStorePickupApiGetPickupLocationsV1 1

Get Pickup Locations filtered by provided Search Request. Pickup Location entities are Immutable object and can not be changed after creation. All modification of Pickup Location…

GET
/V1/inventory/in-store-pickup/pickup-locations/
Get Pickup Locations according to the results of filtration by Search Request.
GetV1InventoryInstorepickupPickuplocations 25 params → 200default

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are inventory-in-store-pickup-api-data-pickup-location-interface (16 properties), inventory-in-store-pickup-api-data-search-request-interface (8 properties), inventory-in-store-pickup-api-data-search-request-filters-interface (8 properties), error-response (5 properties). Each schema is shown below with its type and property counts.

inventory-in-store-pickup-api-data-search-request-area-interface
object
Filter by Distance to the Address. Pickup Locations will be filtered by distance according to the geo-position of the entered address. Required fields for the…
2 properties 2 required
error-errors-item
object
Error details
2 properties
framework-sort-order
object
Data object for sort order.
2 properties 2 required
inventory-in-store-pickup-api-data-search-request-interface
object
Endpoint used to search Pickup Locations by different parameters: - by attribute filters fields @see \Magento\InventoryInStorePickupApi\Api\Data\SearchRequest\…
8 properties 3 required
inventory-in-store-pickup-api-data-search-request-product-info-extension-interface
object
ExtensionInterface class for @see \Magento\InventoryInStorePickupApi\Api\Data\SearchRequest\ProductInfoInterface
inventory-in-store-pickup-api-data-search-request-filters-interface
object
Filter to filter by Fields. Each field may be filtered with different condition type. Supported condition types restricted by @see \Magento\Framework\Api\Searc…
8 properties
error-parameters-item
object
Error parameters item
3 properties
inventory-in-store-pickup-api-data-search-result-interface
object
Search results for providing pickup locations.
3 properties 3 required
error-errors
array
Errors list
inventory-in-store-pickup-api-data-pickup-location-interface
object
Represents sources projection on In-Store Pickup context. Realisation must follow immutable DTO concept. Partial immutability done according to restriction of…
16 properties 1 required
inventory-in-store-pickup-api-data-search-request-extension-interface
object
ExtensionInterface class for @see \Magento\InventoryInStorePickupApi\Api\Data\SearchRequestInterface
1 property
inventory-in-store-pickup-api-data-search-request-filter-interface
object
Filter for Pickup Location search.
2 properties 2 required
inventory-in-store-pickup-api-data-search-request-product-info-interface
object
Product Info Data Transfer Object.
2 properties 1 required
error-response
object
5 properties 1 required
inventory-in-store-pickup-api-data-pickup-location-extension-interface
object
ExtensionInterface class for @see \Magento\InventoryInStorePickupApi\Api\Data\PickupLocationInterface
error-parameters
array
Error parameters list

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

modivo-inventoryinstorepickupapigetpickuplocationsv1-api-openapi.yml Raw ↑

Other APIs MODIVO publishes across the network.

MODIVO Storefront GraphQL API
MODIVO Marketplace Seller API (Mirakl)
MODIVO Catalog Product Render List V1 API
MODIVO Chatbot Order Rest API Order Rest API Service V1 API
MODIVO Checkout Guest Payment Information Management V1 API
MODIVO Checkout Guest Shipping Information Management V1 API
MODIVO Checkout Guest Totals Information Management V1 API
MODIVO Customer Account Management V1 API
MODIVO Directory Country Information Acquirer V1 API
MODIVO Directory Currency Information Acquirer V1 API
MODIVO Eob JWT HTTP Service V1 API
MODIVO Eob My Returns Webhook Webhook V1 API
Where this information came from

This is an independent, third-party profile of MODIVO Inventory In Store Pickup API Get Pickup Locations V1 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.