Chick-fil-A API endpoint
Use Crawlora's Chick-fil-A FAQ API to extract supported public Chick-fil-A data as structured JSON. This page includes request parameters, cURL examples, response schema, error behavior, credit cost, and a Playground link for testing before integration.
/chick-fil-a/faqReturns one page of Chick-fil-A's published customer FAQ corpus (522 entries at time of writing) across 30 categories -- Chick-fil-A One membership, points and rewards, digital ordering and payment, delivery support, sweepstakes terms, and more. Each entry carries the question, the answer as plain text, the answer's original HTML (a fair number of answers use links, lists and tables that plain text loses), and its resolved categories. Every categories[].id is a ready-to-use value for the category filter. search matches over question and answer text and is relevance-ranked; without it entries come back alphabetically so a caller can page through the whole corpus deterministically. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.
Request parameters are generated from the active endpoint catalog. Required values must be sent before Crawlora can call the upstream public web data source.
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| search | string | No | Free-text filter over question and answer text. Results are relevance-ranked when present. | ||
| category | string | No | Comma-separated faq_category term ids, up to 20, from any prior response's categories[].id | ||
| page | integer | No | 1-based page number (default 1) | ||
| per_page | integer | No | Entries per page, 1-100 (default 20) | ||
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/chick-fil-a/faq?page=1" \ -H "x-api-key: $CRAWLORA_API_KEY"
Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.
Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.
| Plan | Price | Included credits | Daily cap | Rate limit | Overage |
|---|---|---|---|---|---|
| Free | $0/mo | 2,000 | 500 daily credits | 5/min | No overage |
| Starter | $9/mo | 20,000 | 5,000 daily credits | 15/min | $0.75/1,000 overage credits when enabled |
| Growth | $29/mo | 100,000 | 25,000 daily credits | 45/min | $0.45/1,000 overage credits when enabled |
| Pro | $79/mo | 400,000 | No daily cap | 120/min | $0.30/1,000 overage credits |
| Business | $199/mo | 1,200,000 | No daily cap | 300/min | $0.20/1,000 overage credits |
| Enterprise | $499/mo | 5,000,000 | No daily cap | 1,000/min | $0.12/1,000 overage credits |
This endpoint is executed through Crawlora's managed scraping infrastructure.
Crawlora does not silently return bad data when the upstream page cannot be used.
| Status | Common failure case |
|---|---|
| 400 | Invalid input or missing required parameter |
| 429 | Plan or endpoint rate limit exceeded |
| 500 | Internal execution error |
| 502 | Upstream platform failed, returned unusable HTML, or served a challenge page that could not be resolved |
When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.
| 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 |
{
"code": 200,
"msg": "OK",
"data": {
"entries": [
{
"id": 41266,
"slug": "delivery-how-it-works",
"question": "How does Chick-fil-A Delivery® work?",
"answer": "Order through the Chick-fil-A App or chick-fil-a.com.",
"answer_html": "<p>Order through the <a href=\"/app\">Chick-fil-A App</a> or chick-fil-a.com.</p>",
"categories": [
{
"id": 58,
"name": "Chick-fil-A Delivery Support FAQS",
"slug": "delivery-support"
}
],
"page_url": "https://www.chick-fil-a.com/faq/delivery-how-it-works",
"modified_at": "2026-08-29T12:00:00"
}
],
"pagination": {
"page": 1,
"per_page": 20,
"total": 522,
"total_pages": 27
},
"source_url": "https://www.chick-fil-a.com/wp-json/wp/v2/faq?page=1&per_page=20",
"fetched_at": "2026-08-30T14:05:00Z"
}
}Request schema
No body schema
Response schema
#/definitions/chickfila.faqResponseDoc
| 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.FAQResponse | No | ||||
| data.entries | array | No | ||||
| data.entries[].answer | string | No | ||||
| data.entries[].answer_html | string | No | ||||
| data.entries[].categories | array | No | ||||
| data.entries[].categories[].id | integer | No | 265 | |||
| data.entries[].categories[].name | string | No | Breakfast | |||
| data.entries[].categories[].slug | string | No | breakfast | |||
| data.entries[].id | integer | No | 41266 | |||
| data.entries[].modified_at | string | No | 2026-08-29T12:00:00 | |||
| data.entries[].page_url | string | No | ||||
| data.entries[].question | string | No | What are the S’mores Milkshake and S’mores Frosted Coffee? | |||
| data.entries[].slug | string | No | smores-milkshake | |||
| 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 | ||||
| msg | unknown | No | Msg is the message that describes the result of the request @example "Request successful" |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/chick-fil-a/faq?page=1" \
-H "x-api-key: $CRAWLORA_API_KEY"Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.
Read Crawlora terms