Picknpayzambia APIpicknpayzambia.com ↗
Access Pick n Pay Zambia promotional catalogs and store locations via 2 endpoints. Retrieve specials with PDF/image URLs, validity dates, and store hours.
What is the Picknpayzambia API?
The Pick n Pay Zambia API provides 2 endpoints for accessing promotional catalog metadata and store location data from picknpayzambia.com. The get_specials endpoint returns catalog objects including PDF and thumbnail URLs, validity dates, and applicable stores, while search_stores returns geo-filtered branch data including addresses, contact details, and opening hours.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/9af6c0b0-ed09-497b-b7a6-12058d576e7b/get_specials' \ -H 'X-API-Key: $PARSE_API_KEY'
Retrieve current promotional catalogs (specials) from Pick n Pay Zambia. Returns catalog metadata including title, validity dates, applicable stores, PDF catalog URL, and thumbnail image URL. The site publishes periodic promotional flyers; this endpoint surfaces whatever is currently active.
No input parameters required.
{
"type": "object",
"fields": {
"total": "integer count of specials",
"specials": "array of promotional catalog objects with title, pdf_url, image_url, validity_dates, stores"
},
"sample": {
"data": {
"total": 1,
"specials": [
{
"title": "16 Years of Serious Value",
"stores": "*Arcades *Crossroads",
"pdf_url": "https://www.picknpayzambia.com/wp-content/uploads/2026/05/PNP989.-AC-June-Catalogue-Phase-4_compressed.pdf",
"image_url": "https://www.picknpayzambia.com/wp-content/uploads/2026/05/PNP989.-AC-June-Catalogue-Phase-4_compressed-1.webp",
"validity_dates": "05 – 24 June 2026"
}
]
},
"status": "success"
}
}About the Picknpayzambia API
Promotional Catalogs
The get_specials endpoint returns all currently published promotional flyers from Pick n Pay Zambia. Each catalog object in the specials array includes a title, pdf_url, image_url, validity_dates, and a stores field indicating which branches the promotion applies to. The endpoint takes no input parameters — it always returns the full set of active catalogs. Note that the underlying flyers are image-based, so individual product prices or SKUs are not broken out as structured fields; the API surfaces catalog-level metadata only.
Store Locations
The search_stores endpoint accepts lat, lng, and radius (in kilometers) to find nearby Pick n Pay Zambia branches. If coordinates are omitted, the search defaults to a center point over Lusaka. Each store object in the stores array includes id, name, address, address2, city, country, lat, lng, phone, email, and a full opening_hours breakdown by day of the week. The max_results parameter caps how many stores are returned in a single call.
Coverage Notes
This API covers promotional catalogs and branch-level location data for Pick n Pay Zambia specifically. It does not cover Pick n Pay operations in South Africa, Zimbabwe, or other markets. Catalog freshness reflects whatever is currently published on the specials page; there is no historical archive of past promotions.
The Picknpayzambia API is a managed, monitored endpoint for picknpayzambia.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when picknpayzambia.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official picknpayzambia.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Display current Pick n Pay Zambia specials with thumbnail previews and PDF download links in a shopping app
- Alert users when new promotional catalogs go live by polling
get_specialsand comparing validity dates - Build a store finder for Zambia shoppers using
search_storeswith GPS coordinates from a mobile device - Show branch-specific promotions by cross-referencing the
storesfield in specials with store IDs fromsearch_stores - Present weekly opening hours for the nearest Pick n Pay Zambia branch using the
opening_hoursfield - Aggregate contact details (phone, email) for all Lusaka-area stores to support a retail directory listing
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Pick n Pay Zambia have an official developer API?+
What does `get_specials` actually return — are individual product prices included?+
title, pdf_url, image_url, validity_dates, and stores. Individual product names, prices, or SKUs are not included because the source publishes image-based flyers rather than structured product data.Does the API cover Pick n Pay stores outside Zambia?+
search_stores endpoint returns Zambian locations and the get_specials endpoint reflects promotions published on picknpayzambia.com. You can fork this API on Parse and revise it to add an endpoint targeting another regional Pick n Pay domain.Is there a way to retrieve historical or expired promotional catalogs?+
get_specials endpoint surfaces only active, currently published catalogs — there is no archive of past promotions. You can fork the API on Parse and revise it to add a history-tracking endpoint that stores previously seen catalogs.Can I filter specials by store or by date range?+
get_specials endpoint takes no filter parameters and returns all current catalogs at once. Store applicability is included in each catalog's stores field, so filtering by store must be done client-side. You can fork the API on Parse and revise it to add server-side filtering parameters.