Chick-fil-A API endpoint
Returns one page of terms for a single Chick-fil-A menu taxonomy, with each term's id, name, slug, parent and how many menu items carry it. This is how to discover the filter ids GET /chick-fil-a/menu accepts. taxonomy must be one of `menu_taxonomy` (customer-facing menu section -- Breakfast, Beverages, Catering Entrées, ... 36 terms), `menu_item_type` (`ITEM`, `ITEM_GROUPING`, `MODIFIER` -- 3 terms), `menu_item_group` (the grouping a variant belongs to, e.g. "Bacon, Egg & Cheese Biscuit" -- 100+ terms), or `nutrition_table_menu` (the grouping used by Chick-fil-A's published nutrition tables -- 18 terms). Terms come back alphabetically.
/chick-fil-a/menu-taxonomyQuery parameters:
taxonomy (required) — which taxonomy to list. One of:
menu_taxonomy — customer-facing menu section (Breakfast, Beverages, Catering Entrées, ...). 36 terms.menu_item_type — ITEM, ITEM_GROUPING, or MODIFIER. 3 terms.menu_item_group — the grouping a variant belongs to, e.g. "Bacon, Egg & Cheese Biscuit". 100+ terms.nutrition_table_menu — the grouping used by Chick-fil-A's published nutrition tables. 18 terms.page (optional, default 1) — 1-based page number.per_page (optional, default 20, max 100) — terms per page.Terms are returned alphabetically. A taxonomy outside the four values above returns a 400.
Response includes taxonomy, terms[], pagination, source_url, and fetched_at. Each term has id, name, slug, item_count, and parent.
| Field | Filled in, of 37 checked | Values in the sample |
|---|---|---|
| id | 37 | |
| name | 37 | “8oz Sauces” and 36 other values |
| slug | 37 | |
| item_count | 37 | 0 to 232, median 29 |
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| taxonomy | string | Yes | Which taxonomy to list. One of menu_taxonomy, menu_item_type, menu_item_group, nutrition_table_menu. Allowed values: menu_taxonomy, menu_item_type, menu_item_group, nutrition_table_menu. | menu_taxonomy | |
| page | integer | No | 1-based page number (default 1) | 1 | |
| per_page | integer | No | Terms per page, 1-100 (default 20) | 100 | |
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/chick-fil-a/menu-taxonomy?taxonomy=menu_taxonomy&page=1" \ -H "x-api-key: $CRAWLORA_API_KEY"
{
"code": 200,
"msg": "OK",
"data": {
"taxonomy": "nutrition_table_menu",
"terms": [
{
"id": 361,
"name": "Breakfast",
"slug": "breakfast",
"item_count": 57
},
{
"id": 362,
"name": "Buns",
"slug": "buns",
"item_count": 4
},
{
"id": 364,
"name": "Catering Entrées",
"slug": "catering-entrees",
"item_count": 7
}
],
"pagination": {
"page": 1,
"per_page": 20,
"total": 18,
"total_pages": 1
},
"source_url": "https://www.chick-fil-a.com/wp-json/wp/v2/nutrition_table_menu?page=1&per_page=20",
"fetched_at": "2026-08-30T13:39:35Z"
}
}Request schema
No body schema
Response schema
#/definitions/chickfila.menuTaxonomyResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | Code is the HTTP status code or a custom code used to indicate the result of the request @example 200 | |||
| data | chickfila.MenuTaxonomyResponse | No | ||||
| data.fetched_at | string | No | ||||
| data.pagination | chickfila.pagination | No | ||||
| data.pagination.page | integer | No | 1 | |||
| data.pagination.per_page | integer | No | 20 | |||
| data.pagination.total | integer | No | 567 | |||
| data.pagination.total_pages | integer | No | 29 | |||
| data.source_url | string | No | ||||
| data.taxonomy | string | No | menu_taxonomy | |||
| data.terms | array | No | ||||
| data.terms[].id | integer | No | 265 | |||
| data.terms[].item_count | integer | No | 232 | ItemCount is how many menu items carry this term, as reported by WordPress's own term counter. | ||
| data.terms[].name | string | No | Breakfast | |||
| data.terms[].parent | integer | No | 0 | Parent is the parent term id for a hierarchical taxonomy, 0 at the top level. | ||
| data.terms[].slug | string | No | breakfast | |||
| msg | unknown | No | Msg is the message that describes the result of the request @example "Request successful" |
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 404 | Not Found | #/definitions/app.Response |
| 429 | Too Many Requests | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/chick-fil-a/menu-taxonomy?taxonomy=menu_taxonomy&page=1" \
-H "x-api-key: $CRAWLORA_API_KEY"