Discover/KFC API
live

KFC APIkfc.com.au

Access KFC Australia store locations, full menus, keyword search, and detailed product nutrition and allergen data via 4 structured JSON endpoints.

Endpoint health
verified 3d ago
get_stores
get_menu
search_menu
get_product_detail
4/4 passing latest checkself-healing
Endpoints
4
Updated
17d ago

What is the KFC API?

The KFC Australia API exposes 4 endpoints covering store discovery, full menu retrieval, keyword search, and per-product detail for every item on kfc.com.au. The get_stores endpoint returns up to 15 nearby locations with coordinates, amenities, and available services. The get_product_detail endpoint goes deeper, returning nutritional information, allergen data, item variants, and modifier options for any product ID.

Try it
Suburb, city, or postcode in Australia.
api.parse.bot/scraper/b5a09d5c-562e-4e11-a251-3ff001f99a98/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/b5a09d5c-562e-4e11-a251-3ff001f99a98/get_stores?location=Sydney' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace kfc-com-au-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""KFC Australia: find stores, search menu, get item details with nutrition."""
from parse_apis.kfc_australia_api import KFCAustralia, Location, Query, ItemNotFound

client = KFCAustralia()

# List nearby stores in Sydney
for store in client.stores.list(location=Location.SYDNEY, limit=3):
    print(store.id, store.name)

# Use a known store to search menu items
store = client.store(id="866")
product = store.products.search(query=Query.ZINGER, limit=3).first()
if product:
    print(product.name, product.price, product.category)

# Get full item detail with nutrition info
try:
    detail = store.items.get(product_id="I-33580-0")
    print(detail.name, detail.caloric_value)
except ItemNotFound as exc:
    print(f"Item not found: {exc}")

# Retrieve the full menu catalog
menu = store.menu.get()
print(menu.id)

print("exercised: stores.list / products.search / items.get / menu.get")
All endpoints · 4 totalmissing one? ·

Get nearby KFC stores by location query (suburb, city, or postcode). Returns up to 15 stores sorted by proximity to the geocoded location. Geo-lookup is proximity-based, so postcode inputs may return nearby stores outside that exact postcode.

Input
ParamTypeDescription
locationstringSuburb, city, or postcode in Australia.
Response
{
  "type": "object",
  "fields": {
    "stores": "array of store objects, each containing id, name, addresses, location (lat/lng), contacts, amenities, and available services/channels"
  },
  "sample": {
    "data": {
      "stores": [
        {
          "id": "802",
          "name": [
            {
              "lang": "en-US",
              "value": "KFC MLC Sydney"
            }
          ],
          "contacts": [
            {
              "key": "phoneNumber",
              "value": "+1 (555) 012-3456"
            }
          ],
          "location": {
            "latitude": -33.8684363,
            "longitude": 151.2092083
          },
          "addresses": [
            {
              "lang": "en-US",
              "address": {
                "city": "Sydney",
                "state": "NSW",
                "pinCode": "2000",
                "addressLines": [
                  "Shop 06, 22-25 Martin Place"
                ]
              }
            }
          ],
          "amenities": [
            "kiosks"
          ]
        }
      ]
    },
    "status": "success"
  }
}

About the KFC API

Store Locations

The get_stores endpoint accepts a location string — suburb, city, or Australian postcode — and returns up to 15 stores sorted by proximity to the geocoded result. Each store object includes id, name, addresses, location (lat/lng), contacts, amenities, and available service channels. Note that proximity-based geo-lookup means results may include stores outside the exact postcode boundary entered.

Menu Data

The get_menu endpoint takes a store_id from get_stores and returns the complete menu as a nested structure of categories, products, and items with prices and availability flags. Menu structure is largely consistent across Australian stores nationally, so the same store_id format (e.g. '866') works across all locations. The search_menu endpoint narrows this down by keyword — query terms like 'zinger' or 'burger' return matching products with name, price, short_description, image URL, url slug, and category. Note that the same product may appear more than once in results if it belongs to multiple menu categories.

Product Detail

The get_product_detail endpoint accepts a product_id (e.g. 'C-33513-prod') sourced from get_menu or search_menu results. It returns the full catalog entry for that product, including all item variants with individual pricing and availability, modifier options (such as meal upgrades or size choices), and a complete nutritional breakdown alongside allergen information. This is the only endpoint that exposes allergen data.

Reliability & maintenanceVerified

The KFC API is a managed, monitored endpoint for kfc.com.au — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when kfc.com.au 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 kfc.com.au 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.

Last verified
3d ago
Latest check
4/4 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Build a KFC store finder app using lat/lng coordinates from get_stores to display nearby locations on a map.
  • Compare prices across menu categories by pulling the full nested menu from get_menu for a given store_id.
  • Filter menu items for allergen-sensitive users by checking allergen fields returned by get_product_detail.
  • Display calorie and nutritional information for any KFC product using the nutrition data in get_product_detail.
  • Power a voice assistant or chatbot that answers product questions using keyword results from search_menu.
  • Track menu availability changes over time by polling get_menu for a specific store and diffing item availability flags.
  • Aggregate modifier and variant pricing for meal customisation tools using the modifiers array in get_product_detail.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo1005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 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.

Frequently asked questions
Does KFC Australia have an official public developer API?+
No. KFC Australia does not publish a public developer API or documentation for third-party access to its menu or store data.
What does `get_stores` return beyond a store's address?+
Each store object includes id, name, addresses, location (lat/lng coordinates), contacts, amenities, and available service channels (such as dine-in, drive-through, or delivery). It does not include real-time wait times or current operating hours status.
Does the API cover ordering, loyalty accounts, or promotional pricing?+
No. The API covers store discovery, menu structure, product search, and product-level nutrition and allergen detail. Order placement, KFC Rewards account data, and promotional or limited-time pricing are not exposed. You can fork this API on Parse and revise it to add an endpoint targeting promotional content if that data is available on kfc.com.au.
Can `search_menu` be filtered by category or dietary requirement?+
The search_menu endpoint matches against product names using a query keyword and returns category as a field in each result, but category-based filtering is not a native input parameter. Results may also contain duplicates when a product belongs to multiple categories. You can fork this API on Parse and revise it to add category or dietary filtering logic on top of the returned data.
How accurate is the postcode-based store search in `get_stores`?+
The endpoint geocodes the input location and returns the 15 closest stores by proximity, not by postcode boundary. A postcode query can return stores in adjacent suburbs or postcodes if those are physically closer than stores within the entered postcode itself.
Page content last updated . Spec covers 4 endpoints from kfc.com.au.
Related APIs in Food DiningSee all →
kroger.com API
Find Kroger grocery store locations across the US organized by state, city, and search parameters. Get detailed store information including directories and specifics for any Kroger location in your area.
mcdonalds.com API
Browse McDonald's full menu and retrieve detailed nutritional information, allergens, and ingredients for any item. Get comprehensive product details to support menu exploration and nutrition-aware applications.
farmersfridge.com API
Access Farmer's Fridge menu data, product details, kiosk locations, and real-time inventory. Browse the full menu or filter by category, retrieve nutrition facts and allergens for individual products, list kiosk locations by access or location type, and check live stock counts at any specific fridge.
kaufland.de API
Search for current deals and discounts at Kaufland Germany stores, viewing detailed pricing information and offer validity periods. Find nearby store locations and browse the latest promotional products all in one place.
crumblcookies.com API
Get Crumbl store locations (addresses, hours, and coordinates), this week’s rotating and classic cookie menu with details, and location-specific “secret menu” items like Hometown Picks and testing flavors.
kingsoopers.com API
Search for King Soopers store locations and browse their product catalog to find items and availability. Note that product searches may have access restrictions that could require additional technical setup to work reliably.
dennys.com API
Find Denny's restaurant locations near you by searching through states, cities, and zip codes, and browse their complete menu with detailed item information organized by category. Discover specific dishes, filter by tags, and get full details about any Denny's location to plan your visit.
smoothieking.com API
Browse Smoothie King's complete menu by category, look up detailed nutrition facts for every smoothie and enhancer, and find nearby store locations. Get comprehensive nutritional information to make informed choices about your smoothie order.