Chick-fil-A API endpoint
Returns one Chick-fil-A menu item, selected by either its numeric id or its slug (supply exactly one of the two -- passing both is rejected). Unlike the listing endpoint, this resolves the item's taxonomy term ids to names, so menu_sections, item_types, item_groups and nutrition_tables each come back as {id, name, slug} triples rather than bare ids. Term resolution is best-effort: if the taxonomy lookups fail the item is still returned with ids and empty names rather than failing the whole call. This item detail carries no price and no nutrition values -- Chick-fil-A does not publish either through this source.
/chick-fil-a/menu-itemQuery parameters:
id (optional) — numeric WordPress post id, e.g. 10613. Supply either id or slug, not both.slug (optional) — item slug, e.g. chick-fil-a-filet. Supply either id or slug, not both.Supplying neither, or both, returns a 400. An id or slug Chick-fil-A does not recognize returns a 404.
Response includes id, slug, name, item_tag, order_url, menu_sections[], item_types[], item_groups[], nutrition_tables[], modified_at, source_url, and fetched_at.
| Field | Filled in, of 2 checked | Values in the sample |
|---|---|---|
| id | 2 | |
| name | 2 | “Entrées” and 1 other value |
| slug | 2 |
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| id | integer | No | Numeric WordPress post id. Supply either id or slug, not both. | 10613 | |
| slug | string | No | Item slug, e.g. from a listing response. Supply either id or slug, not both. | chick-fil-a-filet | |
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/chick-fil-a/menu-item" \ -H "x-api-key: $CRAWLORA_API_KEY"
{
"code": 200,
"msg": "OK",
"data": {
"id": 10613,
"slug": "chick-fil-a-filet",
"name": "Chick-fil-A® Filet",
"item_tag": "CFA_FILET",
"order_url": "https://order.chick-fil-a.com/load-dot-com?itemTag=CFA_FILET",
"menu_sections": [
{
"id": 267,
"name": "Entrées",
"slug": "entrees"
},
{
"id": 323,
"name": "Proteins",
"slug": "proteins"
}
],
"item_types": [
{
"id": 431,
"name": "ITEM",
"slug": "item"
}
],
"item_groups": [
{
"id": 897,
"name": "Filets",
"slug": "filets"
}
],
"nutrition_tables": [
{
"id": 370,
"name": "Proteins",
"slug": "proteins"
}
],
"modified_at": "2026-08-30T04:07:17",
"source_url": "https://www.chick-fil-a.com/wp-json/wp/v2/menu-item?per_page=1&slug=chick-fil-a-filet",
"fetched_at": "2026-08-30T13:38:05Z"
}
}Request schema
No body schema
Response schema
#/definitions/chickfila.menuItemResponseDoc
| 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.MenuItemResponse | No | ||||
| data.fetched_at | string | No | ||||
| data.id | integer | No | 10613 | |||
| data.item_groups | array | No | ||||
| data.item_groups[].id | integer | No | 265 | |||
| data.item_groups[].name | string | No | Breakfast | |||
| data.item_groups[].slug | string | No | breakfast | |||
| data.item_tag | string | No | CFA_FILET | |||
| data.item_types | array | No | ||||
| data.item_types[].id | integer | No | 265 | |||
| data.item_types[].name | string | No | Breakfast | |||
| data.item_types[].slug | string | No | breakfast | |||
| data.menu_sections | array | No | ||||
| data.menu_sections[].id | integer | No | 265 | |||
| data.menu_sections[].name | string | No | Breakfast | |||
| data.menu_sections[].slug | string | No | breakfast | |||
| data.modified_at | string | No | 2026-08-30T08:07:17 | |||
| data.name | string | No | Chick-fil-A® Filet | |||
| data.nutrition_tables | array | No | ||||
| data.nutrition_tables[].id | integer | No | 265 | |||
| data.nutrition_tables[].name | string | No | Breakfast | |||
| data.nutrition_tables[].slug | string | No | breakfast | |||
| data.order_url | string | No | ||||
| data.slug | string | No | chick-fil-a-filet | |||
| data.source_url | string | No | ||||
| 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-item" \
-H "x-api-key: $CRAWLORA_API_KEY"