Product
The kroger_product
data source is designed to retrieve Kroger product pages.
Request samples
In the sample below, we make a request to retrieve the product page for product ID 0021006550000
, specify the delivery location using ZIP code 65401
, set the fulfillment type to delivery
, and assign the store ID to 1100002
.
curl 'https://realtime.oxylabs.io/v1/queries' \
--user 'USERNAME:PASSWORD' \
-H 'Content-Type: application/json' \
-d '{
"source": "kroger_product",
"product_id": "0021006550000",
"delivery_zip": "65401",
"fulfillment_type": "pickup",
"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 product pages.
- 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?