The USA Church Information API is designed to serve structured data about the biggest churches in each U.S. state, based on the dataset from World Population Review. The API enables targeted data retrieval through three main endpoints: one to list all U.S. states in the dataset, one to get the church name for a specific state, and one to retrieve detailed church information using the church’s name as a parameter. This segmented approach ensures efficient, lightweight requests while providing flexibility for deeper data exploration. The API is ideal for researchers, journalists, and organizations seeking insights into religious infrastructure and demographic trends in the United States.
[
{
"states": [
"Utah",
"Michigan",
"Virginia",
"District of Columbia",
"Kentucky",
"California",
"Idaho",
"Mississippi",
"Georgia",
"South Carolina",
"Hawaii",
"Tennessee",
"Iowa",
"Nebraska",
"Oklahoma",
"Pennsylvania",
"Texas",
"Massachusetts",
"Missouri",
"North Dakota",
"Wyoming",
"Illinois",
"Louisiana",
"Colorado",
"Connecticut",
"Maryland",
"Indiana",
"New Jersey",
"Montana",
"Wisconsin",
"North Carolina",
"Minnesota",
"Ohio",
"Arkansas",
"Kansas",
"Alabama",
"New York",
"Arizona",
"Washington",
"Florida",
"Alaska",
"Nevada",
"South Dakota",
"New Mexico",
"West Virginia",
"New Hampshire",
"Oregon"
]
}
]
curl --location --request POST 'https://zylalabs.com/api/9409/usa+church+information+api/17091/get+states+with+churchs' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
[
{
"state": "Ohio",
"church_name": "Crossroads Community Church"
}
]
curl --location --request POST 'https://zylalabs.com/api/9409/usa+church+information+api/17095/get+biggest+church+by+state' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"state":"Required"}'
[
{
"state": "Mississippi",
"church_name": "Pinelake Church",
"average_weekly_attendance": 9091,
"location": "Brandon",
"church_denomination": "Southern Baptist Convention"
}
]
curl --location --request POST 'https://zylalabs.com/api/9409/usa+church+information+api/17096/get+church+info+by+name' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"church_name":"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.
The USA Church Information API provides information about the largest churches in each U.S. state, including their names, locations, and other key details.
Users can retrieve specific church information by querying the API with a church's name to fetch detailed data about that church, including its location and other relevant details.
The USA Church Information API is ideal for researchers, journalists, and organizations seeking insights into religious infrastructure and demographic trends in the United States, allowing them to analyze church distributions and characteristics across different states.
The USA Church Information API provides structured data about the largest churches in each U.S. state, including their names, locations, and other key details. Users can retrieve information by querying specific states or by church name.
Researchers, journalists, and organizations can use the USA Church Information API to gain insights into religious infrastructure and demographic trends in the United States. By leveraging the API's endpoints, users can explore data on church distribution across states and analyze the size and characteristics of these churches.
The "get states with churches" endpoint returns a list of U.S. states. The "get biggest church by state" endpoint returns the largest church's name for a specified state. The "get church info by name" endpoint provides detailed information about a specific church, including its location, attendance, and denomination.
Key fields include "state" and "church_name" in the biggest church endpoint, while the church info endpoint includes "average_weekly_attendance," "location," and "church_denomination," providing comprehensive details about each church.
Each endpoint returns data in a structured JSON format. For example, the church info endpoint returns an array of objects, each containing fields like "state," "church_name," and other relevant details, making it easy to parse and utilize.
The "get biggest church by state" endpoint requires a "state" parameter, while the "get church info by name" endpoint requires a "church_name" parameter. Users must provide valid values from the respective datasets to retrieve accurate results.
The "get states with churches" endpoint provides a list of states. The "get biggest church by state" endpoint offers the name of the largest church in a specified state, while the "get church info by name" endpoint delivers comprehensive details about a specific church, including attendance and denomination.
Users can analyze church distributions by state using the state list, identify the largest churches for demographic studies, and gather detailed church profiles for research or reporting purposes, leveraging the structured data for various applications.
Typical use cases include demographic research, religious studies, community outreach planning, and media reporting on religious infrastructure. Organizations can use the data to understand church attendance trends and regional religious affiliations.
The USA Church Information API sources its data from World Population Review, which is known for its comprehensive demographic datasets. Regular updates and quality checks ensure that the information remains accurate and reliable for users.
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:
55ms
Service Level:
100%
Response Time:
64ms
Service Level:
100%
Response Time:
60ms
Service Level:
100%
Response Time:
72ms
Service Level:
100%
Response Time:
3,770ms
Service Level:
100%
Response Time:
426ms
Service Level:
100%
Response Time:
1,373ms
Service Level:
100%
Response Time:
245ms
Service Level:
100%
Response Time:
327ms
Service Level:
100%
Response Time:
217ms
Service Level:
100%
Response Time:
135ms
Service Level:
100%
Response Time:
2,717ms
Service Level:
100%
Response Time:
863ms
Service Level:
100%
Response Time:
186ms
Service Level:
100%
Response Time:
5,238ms
Service Level:
100%
Response Time:
4,024ms
Service Level:
100%
Response Time:
677ms
Service Level:
100%
Response Time:
1,833ms
Service Level:
99%
Response Time:
1,415ms
Service Level:
100%
Response Time:
1,099ms