Core API use case

A Places of Worship API for global religious-place search

Use one normalized REST API to find nearby places of worship across multiple religions without building your own OpenStreetMap, Overpass, PostGIS and caching pipeline.

What this API is built for

Nearby discovery

Find the nearest place of worship or return a distance-ordered list around any latitude and longitude.

Religion filters

Filter supported categories including christian, muslim, jewish, hindu, buddhist, sikh and shinto, or query all.

Stable lookup

Retrieve a known place later using a stable OSM-backed identifier such as osm:way:164880258.

Three endpoints cover the main workflow

EndpointUse
GET /v1/places/nearestReturn the nearest matching place from a coordinate origin.
GET /v1/places/nearbyReturn nearby matching places ordered by distance with limit and offset.
GET /v1/places/{id}Retrieve a place by stable identifier.

Example: nearest place of worship

curl -H "X-API-Key: $KAIROS_API_KEY" \
"https://kairos.yarumaltech.com/v1/places/nearest?lat=6.96333&lon=-75.41722&radiusKm=8&religion=all"

For marketplace usage, follow the authentication headers provided by RapidAPI or Zyla rather than sending a direct Kairos key.

FAQ

Is this only a church API?

No. Kairos supports multiple religion categories and can search all places of worship without restricting the query to one faith.

Where does the data come from?

Kairos normalizes OpenStreetMap-derived records. Missing source fields are not fabricated, so metadata completeness varies by region.

Can I filter by denomination?

Yes. The optional denomination parameter can be combined with a religion filter when the source data includes that denomination.