Docs

Create Inventory Location

Create a new Inventory Location.

POST

Query

Field selectionChoose which fields should be included in the response. Learn more
string

Comma-separated response fields to include.

Body

Arguments
object
string

The latitude (North-South) component of the geographic coordinate. This field is required if a geoCoordinates container is used. This field is returned if geographical coordinates are set for the location. Example: 33.089805

string

The first line of a street address. This field is required for store and fulfillment center locations. A street address is not required for warehouse locations.

stringrequired

This specifies the unique, seller-defined key (ID) for an inventory location. Max length: 36 (characters). No spaces, but you may use a dash '-' or underscore '_'.

string

Define the function of this inventory location. Typically, an inventory location will serve as a store, warehouse, or fulfillment center, but in some cases, an inventory location may be more than one type.

object

This container is used to set the Global Positioning System (GPS) latitude and longitude coordinates for the inventory location. Geographical coordinates are required for the location of In-Store Pickup inventory.

string

The second line of a street address. This field can be used for additional address information, such as a suite or apartment number. This field will be returned if defined for an inventory location.

string

The longitude (East-West) component of the geographic coordinate. This field is required if a geoCoordinates container is used. This field is returned if geographical coordinates are set for the location. Example: -88.709822

string

The seller-defined name of the inventory location. This name should be a human-friendly name as it will be displayed in In-Store Pickup and Click and Collect listings. A name is not required for warehouse locations. For store locations, this field is not immediately required, but will be required before an offer enabled with the In-Store Pickup or Click and Collect capability can be published.

string

The city in which the inventory location resides. This field is required for store and fulfillment center locations. For warehouse locations, this field is conditionally required as part of a city and stateOrProvince pair if a postalCode is not provided. If a postalCode is provided, the city is derived from the provided postal code and this field is technically optional.

string

Indicate whether the inventory location will be created with the status: ENABLED (inventory can be loaded to location) or DISABLED (inventory can not be loaded to location). If this field is omitted, a successful request will automatically enable the location.

string

The state/province in which the inventory location resides. This field is required for store and fulfillment center locations. For warehouse locations, this field is conditionally required as part of a city and stateOrProvince pair if a postalCode is not provided. If a postalCode is provided, the state or province is derived from the provided zip code and this field is technically optional.

string

This text field is used by the merchant to provide the Website address (URL) associated with the inventory location.

object
string

The postal/zip code of the address. eBay uses postal codes to surface In-Store Pickup items within the vicinity of a buyer's location, and it also uses postal codes (origin and destination) to estimate shipping costs when the seller uses calculated shipping. This field is required for store and fulfillment center locations. For warehouse locations, this field is conditionally required if a city and stateOrProvince pair is not provided. Note: For warehouse locations, city and stateOrProvince pair can be used instead of a postalCode value, and then the postal code is automatically derived from the city and state/province.

string

The county in which the address resides. (optional)

string

The country in which the address resides, represented as two-letter ISO 3166 country code. For example, US represents the United States, and DE represents Germany.

Every app you connect,one REST pattern

Call any app with one REST pattern. MindCloud handles each provider's auth, request shape, and responses for you.

Learn what the Universal API is
One REST patternUse the same request structure across apps like Slack, HubSpot, Salesforce, and thousands more.
Managed connectionsSend a MindCloud connection ID instead of handling provider tokens, refresh logic, and credential storage yourself.
Action-level docsEach action page shows the exact endpoint, required arguments, optional controls, and response behavior for that app version.