The American Casino Data API allows developers and analysts to access casino-related data in a flexible and modular way. With endpoints for retrieving the list of states and additional endpoints for each relevant column (e.g., number of casinos, users can query insights by passing a state parameter. This API supports filtered searches and allows integration into broader data analytics or research applications in gaming, tourism, and economic impact studies.
{"states":["Nevada","Oklahoma","California","Minnesota","Colorado","South Dakota","New York","Washington","Arizona","Mississippi","Michigan","New Mexico","Wisconsin","Louisiana","Iowa","Pennsylvania","Florida","Illinois","Montana","Indiana","Missouri","Kansas","North Dakota","Ohio","Idaho","Oregon","New Jersey","Nebraska","Maryland","West Virginia","Alabama","Arkansas","Delaware","Massachusetts","North Carolina","Virginia","Wyoming","Alaska","Connecticut","Maine","Rhode Island","Texas","District of Columbia","Georgia","Hawaii","Kentucky","New Hampshire","South Carolina","Tennessee","Utah","Vermont"]}
curl --location --request POST 'https://zylalabs.com/api/7063/american+casino+data+api/10979/get+list+of+states+in+the+us' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
{"state_name":"Nevada","total_casinos":232}
curl --location --request POST 'https://zylalabs.com/api/7063/american+casino+data+api/10981/get+number+of+casinos+by+state' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"state":"Required"}'
{"state":"Oklahoma","casinos_names":[]}
curl --location --request POST 'https://zylalabs.com/api/7063/american+casino+data+api/10982/get+casino+names+by+state' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"state":"Required"}'
| 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.
You can filter your queries by passing a state parameter to the API endpoints, allowing you to retrieve specific insights related to that state.
Yes, the American Casino Data API is designed for flexible integration into broader data analytics or research applications, making it suitable for studies in gaming, tourism, and economic impact.
The American Casino Data API provides comprehensive data on the number and legality of casinos across U.S. states for the year 2025. Users can retrieve information such as the total number of casinos in each state and their legal status, allowing for filtered searches and integration into various data analytics or research applications.
The "get list of states" endpoint returns a list of U.S. states. The "get number of casinos by state" endpoint returns the total number of casinos in a specified state for 2025. The "get casino names by state" endpoint provides the names of casinos operating in a specified state.
The key fields include "states" in the list of states endpoint, "state_name" and "total_casinos" in the number of casinos endpoint, and "state" and "casinos_names" in the casino names endpoint.
Each response is structured in JSON format. The list of states returns an array of state names, while the number of casinos and casino names endpoints return objects containing state-specific data, making it easy to parse and utilize.
The primary parameter is the "state" parameter, which must be specified in the "get number of casinos by state" and "get casino names by state" endpoints to retrieve data for a particular U.S. state.
The "get list of states" endpoint provides all U.S. states. The "get number of casinos by state" endpoint offers the total count of casinos, while the "get casino names by state" endpoint lists the names of casinos in the specified state.
Users can customize requests by specifying the "state" parameter in the relevant endpoints, allowing them to retrieve data tailored to specific states of interest.
Typical use cases include analyzing the casino landscape for economic studies, assessing tourism potential, and conducting research on gaming regulations across different states.
If the "get casino names by state" endpoint returns an empty array, it indicates no casinos are present in that state. Users should check the state parameter for accuracy or consider that the state may not have legalized casinos.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used 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.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
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, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
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.
Service Level:
100%
Response Time:
5,617ms
Service Level:
100%
Response Time:
53ms
Service Level:
100%
Response Time:
53ms
Service Level:
100%
Response Time:
62ms
Service Level:
100%
Response Time:
3,174ms
Service Level:
100%
Response Time:
2,104ms
Service Level:
100%
Response Time:
1,780ms
Service Level:
100%
Response Time:
5,655ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
156ms
Service Level:
100%
Response Time:
5,864ms
Service Level:
100%
Response Time:
20,003ms
Service Level:
100%
Response Time:
12,041ms
Service Level:
100%
Response Time:
11,821ms
Service Level:
100%
Response Time:
527ms
Service Level:
100%
Response Time:
1,151ms
Service Level:
100%
Response Time:
779ms
Service Level:
100%
Response Time:
10,646ms
Service Level:
100%
Response Time:
1,440ms
Service Level:
100%
Response Time:
18,580ms