Places of Worship API

API ID 13766

Find churches, mosques, temples, synagogues and other places of worship worldwide by coordinates, religion or denomination.

522 ms avg response

API Documentation

Endpoints

Request
The "Find Nearest Place of Worship" endpoint is designed to assist users in locating the closest places of worship based on their current geographic location or a specified address. It processes input parameters such as latitude and longitude or a specific location string to identify nearby religious institutions, including churches, mosques, synagogues, and temples. Upon successful execution, the endpoint returns a JSON response containing essential details such as the names, addresses, types of worship, distance from the user, and operating hours of these establishments. This endpoint is particularly useful for individuals seeking spiritual solace or community connection while traveling, for event planning, or for researchers analyzing religious demographics in specific regions.
Endpoint ID: 31591
GET https://www.zylalabs.com/api/13766/places+of+worship+api/31591/find+nearest+place+of+worship
INPUT PARAMETERS

Find Nearest Place of Worship — Endpoint Features

Object Description
lat Required Latitude of the search center in decimal degrees. Valid range: -90 to 90.
lon Required Longitude of the search center in decimal degrees. Valid range: -180 to 180.
radiusKm Optional Optional search radius in kilometers. Default: 8. Maximum: 20.
religion Optional Optional religion filter. Default: all. Supported values include christian, muslim, jewish, hindu, buddhist, sikh, shinto, and other.
denomination Optional Optional denomination filter, such as catholic, orthodox, sunni, or another supported denomination slug.

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

lat
lon
radiusKm
religion
denomination
API EXAMPLE RESPONSE
JSON
{
    "data": {
        "id": "osm:way:164880258",
        "name": "Basílica Nuestra Señora de La Merced",
        "location": {
            "lat": 6.9635248,
            "lon": -75.4165179
        },
        "religion": "christian",
        "denomination": "catholic",
        "distance_m": 80.52013441,
        "source": {
            "provider": "openstreetmap",
            "osm_type": "way",
            "osm_id": 164880258
        }
    },
    "meta": {
        "radius_km_used": 10
    }
}
Find Nearest Place of Worship — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/13766/places+of+worship+api/31591/find+nearest+place+of+worship?lat=6.96333&lon=-75.41722&radiusKm=8&religion=all' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
The "Find Nearest Place of Worship" endpoint is designed to assist users in locating the closest religious institutions, such as churches, synagogues, mosques, or temples, based on their current geographical location. By processing the user's latitude and longitude coordinates, the endpoint retrieves a list of nearby worship facilities, including essential details such as names, addresses, service times, and types of worship available. This functionality is particularly useful for individuals seeking community and spiritual connection while traveling, newcomers in a city looking to find a place for reflection, or people wanting to practice their faith nearby, ultimately enhancing access to religious resources and fostering community engagement.
Endpoint ID: 31592
GET https://www.zylalabs.com/api/13766/places+of+worship+api/31592/find+nearest+place+of+worship
INPUT PARAMETERS

Find Nearest Place of Worship — Endpoint Features

Object Description
lat Required Latitude of the search center in decimal degrees. Valid range: -90 to 90.
lon Required Longitude of the search center in decimal degrees. Valid range: -180 to 180.
radiusKm Optional Optional search radius in kilometers. Default: 8. Maximum: 20.
religion Optional Optional religion filter. Default: all. Supported values include christian, muslim, jewish, hindu, buddhist, sikh, shinto, and other.
denomination Optional Optional denomination filter, such as catholic, orthodox, sunni, or another supported denomination slug.
limit Optional Maximum number of results to return. Default: 50. Minimum: 1. Maximum: 200.
offset Optional Number of results to skip for pagination. Default: 0.

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

lat
lon
radiusKm
religion
denomination
limit
offset
API EXAMPLE RESPONSE
JSON
{
    "data": [
        {
            "id": "osm:way:164880258",
            "name": "Basílica Nuestra Señora de La Merced",
            "location": {
                "lat": 6.9635248,
                "lon": -75.4165179
            },
            "religion": "christian",
            "denomination": "catholic",
            "distance_m": 80.52013441,
            "source": {
                "provider": "openstreetmap",
                "osm_type": "way",
                "osm_id": 164880258
            }
        },
        {
            "id": "osm:node:4512936427",
            "name": "Capilla de San Luis",
            "location": {
                "lat": 6.9641614,
                "lon": -75.4188194
            },
            "religion": "christian",
            "denomination": "catholic",
            "distance_m": 199.22549471,
            "source": {
                "provider": "openstreetmap",
                "osm_type": "node",
                "osm_id": 4512936427
            }
        },
        {
            "id": "osm:node:9416980218",
            "name": "Parroquia La Inmaculada",
            "location": {
                "lat": 6.9657231,
                "lon": -75.4191998
            },
            "religion": "christian",
            "denomination": "roman_catholic",
            "distance_m": 343.37210802,
            "source": {
                "provider": "openstreetmap",
                "osm_type": "node",
                "osm_id": 9416980218
            }
        },
        {
            "id": "osm:node:4522486808",
            "name": "Parroquia El Carmen",
            "location": {
                "lat": 6.9576923,
                "lon": -75.4147571
            },
            "religion": "christian",
            "denomination": "roman_catholic",
            "distance_m": 680.29028748,
            "source": {
                "provider": "openstreetmap",
                "osm_type": "node",
                "osm_id": 4522486808
            }
        },
        {
            "id": "osm:node:6202524785",
            "name": "Capilla San Nicolás",
            "location": {
                "lat": 6.9671831,
                "lon": -75.4223389
            },
            "religion": "christian",
            "denomination": "roman_catholic",
            "distance_m": 708.19617987,
            "source": {
                "provider": "openstreetmap",
                "osm_type": "node",
                "osm_id": 6202524785
            }
        }
    ],
    "meta": {
        "radius_km_used": 10,
        "count": 5,
        "limit": 50,
        "offset": 0
    }
}
Find Nearest Place of Worship — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/13766/places+of+worship+api/31592/find+nearest+place+of+worship?lat=6.96333&lon=-75.41722&radiusKm=8&religion=all&limit=50&offset=Optional' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
The "Get Place of Worship by ID" endpoint allows clients to retrieve detailed information about a specific place of worship using its unique identifier (ID). This API call returns a structured response that includes essential attributes such as the name, address, type of worship (e.g., church, mosque, synagogue), contact details, and operational hours of the place of worship. This endpoint is particularly useful for developers building applications that facilitate community engagement, tourism, or religious studies, as it enables users to obtain precise data on worship locations for planning visits, events, or community outreach programs.
Endpoint ID: 31593
GET https://www.zylalabs.com/api/13766/places+of+worship+api/31593/get+place+of+worship+by+id
INPUT PARAMETERS

Free test requests remaining: 3 of 3.

API EXAMPLE RESPONSE
JSON
{
    "data": {
        "id": "osm:way:164880258",
        "name": "Basílica Nuestra Señora de La Merced",
        "location": {
            "lat": 6.9635248,
            "lon": -75.4165179
        },
        "religion": "christian",
        "denomination": "catholic",
        "distance_m": null,
        "source": {
            "provider": "openstreetmap",
            "osm_type": "way",
            "osm_id": 164880258
        }
    }
}
Get Place of Worship by ID — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/13766/places+of+worship+api/31593/get+place+of+worship+by+id&DATA=Required' --header 'Authorization: Bearer YOUR_API_KEY' 


    

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 Places of Worship 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.

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

🚀 Enterprise Plan

Starts at
$ 10,000/Year


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

Overview

Find churches, mosques, temples, synagogues and other places of worship worldwide by coordinates, religion or denomination.

Places of Worship API FAQs

Each endpoint returns information about places of worship, including their names, locations (latitude and longitude), religion, denomination, and distance from the specified coordinates. The data is structured in a consistent JSON format.

Key fields in the response include "id" (stable public identifier), "name" (place name), "location" (coordinates), "religion" (type of worship), "denomination" (specific branch), "distance_m" (distance in meters), and "source" (data provider information).

Users can customize their requests using parameters such as latitude, longitude, radius (in kilometers), religion, and denomination. Optional filters allow for more specific searches based on user needs.

The response data is organized into two main sections: "data," which contains the details of the place of worship, and "meta," which includes metadata like the radius used for the search. This structure allows for easy access to both the results and the context of the query.

The data is derived from OpenStreetMap, ensuring a broad and diverse coverage of places of worship. Kairos maintains data accuracy by preserving source information and not fabricating unavailable fields.

Typical use cases include travel applications, local discovery platforms, faith and community services, mapping tools, directories, accessibility services, and research products, allowing users to find places of worship based on their location and preferences.

Users can utilize the returned data by integrating it into applications for location-based services, filtering results by religion or denomination, and displaying nearby places of worship on maps or directories, enhancing user experience and accessibility.

Ensures data quality by sourcing information from OpenStreetMap and implementing checks for completeness and accuracy. The API preserves source information, allowing users to verify the reliability of the data provided.

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