Availabilities

Retrieving all availability information for a site

get

Retrieves all availability information for a specified site.

Note: When a product bundle is retrieved, availability is returned both for its particular products and for the bundle as a whole. The bundle availability is equal to the lowest availability found in its products.


Required scopes

  • No specific scopes are required.

  • Scope availability.availability_view_by_vendor allows to fetch just the availabilities belonging to the vendor.

Authorizations
OAuth2clientCredentialsRequired
Token URL:
Available scopes:
  • : view_availability
  • : manage_availability
Path parameters
tenantstringRequired

Your Emporix tenant name.

Note: The tenant name should always be provided in lowercase.

Example: testtenant
sitestringRequired

Site code, defined when the site is created.

Example: shop1
Query parameters
pageSizenumberOptional

Number of items to be retrieved per page.

Default: 20000Example: 100
pageNumbernumberOptional

Page number to be retrieved. The number of the first page is 1.

Note: If the pageNumber parameter is passed, size of the pages must be specified in the pageSize parameter.

Default: 1Example: 5
Responses
200

The request was successful. A list of availabilities is returned.

application/json
get
/availability/{tenant}/availability/site/{site}

Retrieving product availabilities for a site

post

Retrieves availabilities for specified products on a specified site.


Required scopes

  • No specific scopes are required.

  • Scope availability.availability_view_by_vendor allows to fetch just the availabilities belonging to the vendor.

Authorizations
OAuth2clientCredentialsRequired
Token URL:
Available scopes:
  • : view_availability
  • : manage_availability
Path parameters
tenantstringRequired

Your Emporix tenant name.

Note: The tenant name should always be provided in lowercase.

Example: testtenant
Query parameters
sitestringOptional

Site code, defined when the site is created. If it's not provided, then availabilities for all sites are returned.

Example: shop1
pageSizenumberOptional

Number of items to be retrieved per page.

Default: 20000Example: 100
pageNumbernumberOptional

Page number to be retrieved. The number of the first page is 1.

Note: If the pageNumber parameter is passed, size of the pages must be specified in the pageSize parameter.

Default: 1Example: 5
Bodystring[]
string[]Optional

IDs of products for which the locations should be retrieved.

Responses
200

The request was successful. A list of availabilities is returned.

application/json
post
/availability/{tenant}/availability/search

Retrieving a product availability

get

Retrieves a specified product availability details.

Required scopes

  • No specific scopes are required.

  • Scope availability.availability_view_by_vendor allows to fetch just the availabilities belonging to the vendor.


Authorizations
OAuth2clientCredentialsRequired
Token URL:
Available scopes:
  • : view_availability
  • : manage_availability
Path parameters
tenantstringRequired

Your Emporix tenant name.

Note: The tenant name should always be provided in lowercase.

Example: testtenant
productIdstringRequired

Product unique identifier, generated when the product is created through the Product Service.

Example: 5f7c996173fc281cdd412345
sitestringRequired

Site code, defined when the site is created.

Example: shop1
Responses
200

The request was successful. The product availability details are returned.

application/json
get
/availability/{tenant}/availability/{productId}/{site}

Creating a new availability for a product

post

Creates a new availability for a specified product.

Note: We recommend not to create a new product availability for a site named main. A site named main works as an aggregator of availability data from other sites. It's not possible to later retrieve availability for a single site when it's called main.


Required scopes

  • availability.availability_manage

  • availability.availability_manage_by_vendor - allows to create availabilities for products belonging to the vendor

Required scopes
This endpoint requires the following scopes:
  • : manage_availability
Authorizations
OAuth2clientCredentialsRequired
Token URL:
Path parameters
tenantstringRequired

Your Emporix tenant name.

Note: The tenant name should always be provided in lowercase.

Example: testtenant
productIdstringRequired

Product unique identifier, generated when the product is created through the Product Service.

Example: 5f7c996173fc281cdd412345
sitestringRequired

Site code, defined when the site is created.

Example: shop1
Body
stockLevelnumberOptional

Stock level of the product, expressed as a number.

Example: 10
availablebooleanOptional

Flag indicating whether the product is available.

Example: true
popularityintegerOptional

Popularity of the product, expressed as a number.

Example: 5
distributionChannelstring · enumOptional

Name of the product distribution channel.

Example: ASSORTMENTPossible values:
Responses
post
/availability/{tenant}/availability/{productId}/{site}

Upserting availability information of a product

put

Updates a specified product availability details, or crates a new availability if it doesn't exist yet.

Note: There is no possibility to update a product bundle availability - it is always equal to the lowest availability found in the bundled products.


Required scopes

  • availability.availability_manage

  • availability.availability_manage_by_vendor - allows to update availabilities belonging to the vendor

Required scopes
This endpoint requires the following scopes:
  • : manage_availability
Authorizations
OAuth2clientCredentialsRequired
Token URL:
Path parameters
tenantstringRequired

Your Emporix tenant name.

Note: The tenant name should always be provided in lowercase.

Example: testtenant
productIdstringRequired

Product unique identifier, generated when the product is created through the Product Service.

Example: 5f7c996173fc281cdd412345
sitestringRequired

Site code, defined when the site is created.

Example: shop1
Body
stockLevelnumberOptional

Stock level of the product, expressed as a number.

Example: 10
availablebooleanOptional

Flag indicating whether the product is available.

Example: true
popularityintegerOptional

Popularity of the product, expressed as a number.

Example: 5
distributionChannelstring · enumOptional

Name of the product distribution channel.

Example: ASSORTMENTPossible values:
Responses
put
/availability/{tenant}/availability/{productId}/{site}

Deleting availability information of a product

delete

Deletes a specified product availability.

Note: There is no possibility to delete a product bundle availability - it is always equal to the lowest availability found in the bundled products.


Required scopes

  • availability.availability_manage

  • availability.availability_manage_by_vendor - allows to delete belonging to the vendor

Required scopes
This endpoint requires the following scopes:
  • : manage_availability
Authorizations
OAuth2clientCredentialsRequired
Token URL:
Path parameters
tenantstringRequired

Your Emporix tenant name.

Note: The tenant name should always be provided in lowercase.

Example: testtenant
productIdstringRequired

Product unique identifier, generated when the product is created through the Product Service.

Example: 5f7c996173fc281cdd412345
sitestringRequired

Site code, defined when the site is created.

Example: shop1
Responses
delete
/availability/{tenant}/availability/{productId}/{site}

No content

Last updated

Was this helpful?