URL
You can get Kroger results by providing your own URLs to our service. We can return the HTML for any Kroger page you like.
Request samples
The sample below demonstrates how to retrieve a Kroger search results page based on a specific product query, price range, and store location.
curl 'https://realtime.oxylabs.io/v1/queries' \
--user 'USERNAME:PASSWORD' \
-H 'Content-Type: application/json' \
-d '{
"source": "kroger",
"url": "https://www.kroger.com/search?query=adidas&price=10.00-15.00",
"store_id": "01100002"
}'
We use synchronous Realtime integration method in our examples. If you would like to use Proxy Endpoint or asynchronous Push-Pull integration, refer to the integration methods section.
Request parameter values
Generic
Basic setup and customization options for scraping Kroger marketplace.
- mandatory parameter
Localization
Customize results based on store locations, delivery areas, and preferred fulfillment methods.
store_id
Specify a store. See the available values here. The ID must start with '0'.
-
Required when fulfillment_type
is set to pickup
or in_store
.
delivery_zip
Specify delivery location ZIP code.
-
Required when fulfillment_type
is set to delivery
or ship
.
fulfillment_type
Specify order fulfillment method. Available values: ship
, pickup
, delivery
, in_store
.
pickup
(if only store_id
is provided)
Requires store_id
for pickup
and in_store
, or delivery_zip
for delivery
and ship
.
Dependecies explained:
pickup
andin_store
values use thestore_id
parameter to determine the correct store.delivery
andship
use thedelivery_zip
parameter to specify the delivery location.If only
store_id
is provided, andfulfillment_type
is not specified, the default type ispickup
.
If the fulfillment_type
and store_id
/delivery_zip
combination is invalid (unsupported by Kroger), the scraped page will return with a 404 status.
Last updated
Was this helpful?