{"countries":["United States","Canada","Puerto Rico","United States Virgin Islands","Costa Rica","Australia","Guam","Japan","Netherlands","Panama","Germany","France","El Salvador","Sweden","Guatemala","Cura\u00e7ao","United Kingdom","Hong Kong","Bahamas","New Zealand","Switzerland","Ireland","Austria","Belgium","Brazil","Singapore","Spain","Denmark","Philippines","Malaysia","Norway","Taiwan","Andorra","Finland","Thailand","Italy","Aruba","Luxembourg","Venezuela","Mexico","Cuba","Turkey","Argentina","Macau","Serbia","South Korea","Hungary","China","Chile","Indonesia","Portugal","Greece","Uruguay","Martinique","Czech Republic","Guadeloupe","Poland","Monaco","Brunei","Morocco","Northern Mariana Islands","Israel","Slovenia","Saudi Arabia","Kuwait","New Caledonia","Oman","Egypt","Bulgaria","Bahrain","Latvia","United Arab Emirates","Estonia","Romania","Malta","Colombia","Slovakia","South Africa","Qatar","Honduras","Sint Maarten","Croatia","Samoa","Fiji","Liechtenstein","Lithuania","India","Peru","Jordan","Paraguay","Dominican Republic","French Polynesia","Trinidad and Tobago","Ukraine","Cyprus","Jersey","Ecuador","R\u00e9union","Isle of Man","Suriname","Moldova","Nicaragua","Lebanon","Pakistan","Georgia","Gibraltar","Azerbaijan","French Guiana","American Samoa","Mauritius","Vietnam","Saint Martin","Western Sahara"]}
curl --location --request POST 'https://zylalabs.com/api/6027/mcdonald%27s+locator+api/8118/get+all+countries+with+mcdonalds' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
[{"number_of_restaurants":223}]
curl --location --request POST 'https://zylalabs.com/api/6027/mcdonald%27s+locator+api/8119/get+mcdonald%27s+count+by+country' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"country":"Required"}'
{"United States":"San Bernardino, California"}
curl --location --request POST 'https://zylalabs.com/api/6027/mcdonald%27s+locator+api/8120/get+first+mcdonald+location+per+country' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"country":"Required"}'
{"date_of_first_outlet":"May 15, 1940"}
curl --location --request POST 'https://zylalabs.com/api/6027/mcdonald%27s+locator+api/8121/get+date+of+first+mcdonalds+by+country' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"country":"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 McDonald's Locator 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 McDonald's Locator API is specifically designed to handle data related to the global presence of McDonald's restaurants. It processes information regarding countries and territories that have at least one McDonald's outlet.
The McDonalds Locator API allows you to retrieve structured data about McDonald's restaurants worldwide, including details about countries with outlets, the total number of restaurants, and the years of operation.
The API processes information specifically for countries and territories that have at least one McDonald's outlet, ensuring that users can access relevant data for each location.
Yes, the McDonalds Locator API is designed for developers, providing structured access to global restaurant data, making it easy to integrate into various applications.
Yes, you can use the API to query and retrieve the number of McDonald's restaurants in a specific country, along with other relevant details.
The McDonalds Locator API allows you to retrieve structured data about the presence of McDonald's restaurants worldwide, including information about countries and territories with McDonald's outlets, the number of restaurants in each location, and the years of operation.
Each endpoint returns structured data related to McDonald's restaurants. For example, the "get all countries" endpoint returns a list of countries, while "get McDonald's count by country" provides the total number of restaurants in a specified country.
Key fields include "countries" for the list of nations, country names as keys for counts, and "date_of_first_outlet" for the establishment date of the first McDonald's in a country.
The endpoints require a country parameter for specific queries, such as retrieving the number of restaurants or the first location. Users must specify the country name accurately to receive the correct data.
The response data is organized in JSON format. For instance, the count endpoint returns a JSON object with country names as keys and their respective restaurant counts as values.
Typical use cases include market analysis, location-based services, and business intelligence applications that require insights into McDonald's global presence and restaurant distribution.
Data accuracy is maintained through regular updates and quality checks, ensuring that the information about McDonald's locations and counts reflects the latest operational status.
Each endpoint provides specific information: the "get all countries" endpoint lists countries, "get McDonald's count" gives restaurant totals, "get first location" shows the first outlet's address, and "get date of first McDonald's" reveals the establishment date.
Users can utilize the returned data by integrating it into applications for location services, analytics, or reporting. For example, they can visualize restaurant distribution or track growth trends in specific regions.
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