US Church Database API API ID: 9406

Seamlessly retrieve engaging content from US churches to enhance your applications.
Use this API from your AI agent via MCP
Works with OpenClaw, Claude Code/Desktop, Cursor, Windsurf, Cline and any MCP-compatible AI client.
Docs & setup
Create a skill by wrapping this MCP: https://mcp.zylalabs.com/mcp?apikey=YOUR_ZYLA_API_KEY

The US Church Database 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.

API Documentation

Endpoints


This endpoint allows users to retrieve the list of U.S. states included in the dataset.


                                                                            
POST https://pr220-testing.zylalabs.com/api/9406/us+church+database+api/17082/get+states+with+churchs
                                                                            
                                                                        

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

This endpoint does not require any input parameters.


API EXAMPLE RESPONSE

[
    {
        "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"
        ]
    }
]

Get states with churchs - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/9406/us+church+database+api/17082/get+states+with+churchs' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'


This endpoint enables users to fetch the name of the largest church in a given state. To use it, you must indicate a state as a parameter. You can get them form the first endpoint.


                                                                            
POST https://pr220-testing.zylalabs.com/api/9406/us+church+database+api/17084/get+biggest+church+by+state
                                                                            
                                                                        

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

state

API EXAMPLE RESPONSE

[
    {
        "state": "Ohio",
        "church_name": "Crossroads Community Church"
    }
]

Get biggest church by state - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/9406/us+church+database+api/17084/get+biggest+church+by+state' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"state":"Required"}'


This endpoint allows users to get all available information about a specific church. To use it, you must indicate a church name as a parameter. You can get them from the second endpoint.


                                                                            
POST https://pr220-testing.zylalabs.com/api/9406/us+church+database+api/17086/get+church+info+by+name
                                                                            
                                                                        

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

church_name

API EXAMPLE RESPONSE

[
    {
        "state": "Mississippi",
        "church_name": "Pinelake Church",
        "average_weekly_attendance": 9091,
        "location": "Brandon",
        "church_denomination": "Southern Baptist Convention"
    }
]

Get church info by name - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/9406/us+church+database+api/17086/get+church+info+by+name' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"church_name":"Required"}'


API Access Key & Authentication

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 US Church Database API simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

🚀 Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Customer favorite features

  • ✔︎ Only Pay for Successful Requests
  • ✔︎ Free 7-Day Trial
  • ✔︎ Multi-Language Support
  • ✔︎ One API Key, All APIs.
  • ✔︎ Intuitive Dashboard
  • ✔︎ Comprehensive Error Handling
  • ✔︎ Developer-Friendly Docs
  • ✔︎ Postman Integration
  • ✔︎ Secure HTTPS Connections
  • ✔︎ Reliable Uptime

US Church Database API FAQs

The US Church Database 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 US Church Database 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 US Church Database 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 US Church Database 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 US Church Database 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.

General FAQs

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.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

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.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

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.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs