Giant Food APIgiantfood.com ↗
Find Giant Food stores by ZIP code and retrieve current weekly ad sale prices, validity dates, and items per publication via a simple 2-endpoint API.
What is the Giant Food API?
The Giant Food API provides 2 endpoints for locating stores and retrieving weekly circular data. Use find_stores to get a ranked list of nearby Giant Food locations from any 5-digit US ZIP code, then call get_weekly_ad with a store_code to pull every advertised item, its sale price in USD, and the validity window for each active publication. The response includes fields like price, sale_story, valid_from, and valid_to.
curl -X GET 'https://api.parse.bot/scraper/4debfa93-2aa2-4fe7-a75f-587948a641b4/find_stores?zip_code=22551' \ -H 'X-API-Key: $PARSE_API_KEY'
Lists Giant Food stores near a 5-digit US ZIP code, ordered nearest first, with address, coordinates, distance in miles and the number of current ad flyers each store has. Returns one object with a stores array in a single round trip. The site always returns the nearest stores, even for a ZIP far from any store, so an empty list is not expected. Each store's store_code is the input to get_weekly_ad.
| Param | Type | Description |
|---|---|---|
| zip_coderequired | string | 5-digit US ZIP code to search around, leading zeros preserved. |
{
"type": "object",
"fields": {
"stores": "array of nearby stores, nearest first",
"zip_code": "the ZIP code searched",
"stores[].store_code": "4-digit store code (string), pass to get_weekly_ad",
"stores[].flyer_count": "number of current ad flyers for the store",
"stores[].distance_miles": "distance from the ZIP in miles (number)"
},
"sample": {
"data": {
"stores": [
{
"city": "Spotsylvania",
"name": "Giant Food - Spotsylvania",
"state": "VA",
"address": "10346 Courthouse Road",
"latitude": 38.2452697754,
"longitude": -77.5291595459,
"store_code": "0256",
"flyer_count": 1,
"postal_code": "22553",
"distance_miles": 9.05857
}
],
"zip_code": "22551"
},
"status": "success"
}
}About the Giant Food API
Store Discovery
The find_stores endpoint accepts a 5-digit zip_code and returns a stores array sorted by proximity. Each store object includes a 4-digit store_code (the key to pass into the weekly ad endpoint), a distance_miles value, a full address, coordinates, and a flyer_count indicating how many active ad publications that location currently has. No authentication or additional context is required — a ZIP code is the only input.
Weekly Ad Data
The get_weekly_ad endpoint takes a required store_code and returns a publications array. Each publication carries valid_from and valid_to ISO dates, a total_items count before filtering, and an items array. Each item includes a numeric price in USD when the deal is a straightforward markdown. When the offer is structured as a multi-item promotion (e.g., buy-one-get-one), the price field is null and the deal is expressed in the sale_story text field instead. An optional category parameter (e.g., Produce, Meat, Dairy, Grocery) filters items server-side and updates item_count on the publication object accordingly.
Filtering and Context
The category filter applies to item labels as Giant Food categorizes them in the circular. If you query without a category, all items across all active publications are returned. The optional zip_code parameter on get_weekly_ad passes geographic context alongside the store_code but is not required for a valid response — omitting it still returns the full weekly ad.
Coverage Notes
Giant Food operates stores across Maryland, Virginia, Delaware, and Washington D.C. The API reflects the current weekly ad cycle; items rotate as new circulars go live. The publications_available field on the response tells you how many total publications exist for the store at query time, which may differ from the number actually returned if the store's flyer count changes mid-cycle.
The Giant Food API is a managed, monitored endpoint for giantfood.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when giantfood.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 giantfood.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?+
- Build a grocery price-comparison tool using sale prices from get_weekly_ad across multiple nearby stores
- Alert shoppers when a specific category (e.g., Meat) has new sale items by polling publications[].valid_from
- Aggregate weekly deal data across all Giant Food stores in a region by iterating store_codes from find_stores
- Display the nearest Giant Food location and its current flyer count in a local shopping app using find_stores
- Track price history for recurring items by storing publications[].items[].price over successive ad cycles
- Filter weekly ad results by Produce or Dairy category to surface deals for specific dietary shopping lists
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.