{
"states": [
"Alabama",
"Alaska",
"Arizona",
"Arkansas",
"California",
"Colorado",
"Connecticut",
"Delaware",
"District of Columbia",
"Florida",
"Georgia",
"Hawaii",
"Idaho",
"Illinois",
"Indiana",
"Iowa",
"Kansas",
"Kentucky",
"Louisiana",
"Maine",
"Maryland",
"Massachusetts",
"Michigan",
"Minnesota",
"Mississippi",
"Missouri",
"Montana",
"Nebraska",
"Nevada",
"New Hampshire",
"New Jersey",
"New Mexico",
"New York",
"North Carolina",
"North Dakota",
"Ohio",
"Oklahoma",
"Oregon",
"Pennsylvania",
"Rhode Island",
"South Carolina",
"South Dakota",
"Tennessee",
"Texas",
"Utah",
"Vermont",
"Virginia",
"Washington",
"West Virginia",
"Wisconsin",
"Wyoming"
]
}
curl --location --request POST 'https://zylalabs.com/api/9840/fastfood+preferences+api/18478/obtain+list+of+us+states' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
{
"state": "Florida",
"top_chain": "Chick-Fil-A"
}
curl --location --request POST 'https://zylalabs.com/api/9840/fastfood+preferences+api/18480/get+top+rated+fast+food+chain' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"state":"Required"}'
{
"state": "Florida",
"most_searched_chain": [
"McDonald's",
"Chick-Fil-A",
"Starbucks"
]
}
curl --location --request POST 'https://zylalabs.com/api/9840/fastfood+preferences+api/18483/get+most+searched+fast+food+chains' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"state":"Required"}'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the FastFood Preferences API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
(Save 2 months with annual billing 🎉)
The FastFood Preferences API enables developers, researchers, and food industry analysts to query fast food popularity data in the United States by state. Instead of retrieving all the information in one bulk request, the API is designed with focused endpoints to allow granular queries: Retrieve the full list of U.S. states covered by the dataset. Fetch the top-rated fast food chain for a given state. Retrieve the most searched fast food chain in a given state. This structured approach provides efficiency and flexibility, making it easier to integrate food popularity insights into dashboards, analytics tools, or recommendation systems.
You can integrate the FastFood Preferences API into your application to provide insights on fast food popularity. This can be useful for creating dashboards, analytics tools, or recommendation systems that help users discover trending fast food options based on state-specific data.
The FastFood Preferences API allows you to retrieve structured data about the most popular fast food chains across U.S. states. You can fetch the full list of U.S. states covered by the dataset, the top-rated fast food chain for a specific state, and the most searched fast food chain in a given state. This data can be utilized for analytics, dashboards, or recommendation systems.
The FastFood Preferences API has three endpoints. The first returns a list of U.S. states. The second provides the top-rated fast food chain for a specified state, while the third returns the most searched fast food chains in that state. Each endpoint delivers structured JSON data relevant to fast food trends.
The key fields in the response data include "states" for the list of U.S. states, "top_chain" for the top-rated fast food chain, and "most_searched_chain" for the list of popular fast food chains in a state. These fields provide essential insights into fast food preferences.
The endpoints require specific parameters, such as the state name for the top-rated and most searched fast food chain endpoints. Users must provide valid state names to receive accurate data. The first endpoint does not require parameters as it retrieves all states.
The response data is organized in JSON format. For example, the top-rated fast food chain endpoint returns an object containing the "state" and "top_chain" fields, while the most searched chains endpoint returns the "state" and an array of "most_searched_chain" values, making it easy to parse and utilize.
Typical use cases include market analysis, consumer behavior studies, and developing recommendation systems. Businesses can leverage this data to identify trending fast food options in specific states, enhancing marketing strategies and product offerings.
Data accuracy is maintained through regular updates and quality checks. The API aggregates real-time trends from various sources, ensuring that the information reflects current consumer preferences and behaviors in the fast food industry.
Users can integrate the returned data into dashboards or analytics tools to visualize trends. For instance, displaying the top-rated fast food chains by state can help businesses tailor their marketing efforts or menu offerings based on regional preferences.
Users can expect consistent data patterns, such as a single top-rated chain per state and a list of multiple searched chains. This structure allows for straightforward comparisons and insights into regional fast food popularity trends.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund