Real-time ecommerce request

To make a simple request for a single market search page, use the /realtime/ecommerce endpoint and include the Amazon/Walmart URL.

Request Options

Parameter
Required
Description

vendor

Required

ENUM | walmart, amazon

url

Required

String | any walmart/amazon URL (product, search, category, etc)

country

Optional (default = all)

String | Country used to access the target URL, use ISO Alpha-2 Country Codes i.e. US, DE, GB

state

Optional

String | For targeting US states (does not include regions or territories in other countries). Two-letter state code, e.g. NY, IL, etc.

city

Optional

String | For targeting large cities and metro areas around the globe. When targeting major US cities, you must include state as well. Click here for a list of available cities.

zip

optional

String | A 5-digit US zip code. If provided, the closest store to the provided zip code is selected.

locale

Optional (default = en)

String | LCID standard locale used for the URL request. Alternatively, user can use auto for automatic locale based on country targeting.

parse

Optional (default = false)

Boolean | true | false Instructs Nimble whether to structure the results into a JSON format or return the raw HTML.

Walmart Options

Parameter
Required
Description

store

optional (zipcode is required when using store)

String | If not provided, the closest store to the provided zip code is selected.

Nimble APIs requires that a base64 encoded credential string be sent with every request to authenticate your account. For detailed examples, see E-commerce API Authentication.

Request Example: product page

To make a simple request for a single market page, use the /realtime/ecommerce endpoint with the following syntax:

Request Example: product search

This is example for Product Search requests - use the same endpoint and parameters as a simple product page request, and simply require a different URL to be sent in the URL field.

To make a simple request for a single market search page, use the /realtime/ecommerce endpoint with the following syntax:

Response

Headers

X-Task-ID: string

Payload examples:

If parsing was disabled or omitted in the request, the result data will be the raw HTML of the requested page. If parsing was enabled, a JSON object with a parsed version of the page will be delivered, with the raw HTML included under the html_content property.

200 OK

500 Error

400 Input Error

Response Codes

Status
Description

200

OK

400

The requested resource could not be reached

401

Unauthorized/invalid credental string

500

Internal service error

501

An error was encountered by the proxy service

Last updated