Comprehensive Islamic Center Database & Prayer Times API
Mosque.API is an open-source platform that enables mosque leaders to manage and update their mosque information, which can then be integrated into prayer apps, mosque finders, and other Islamic applications. It provides a centralized database for mosque data including prayer times, capacity information, events, services, and real-time updates.
- Website: https://mosque.api
- API Base URL:
https://api.mosque.api - Documentation: docs.mosque.api · Getting Started · Try it · Examples
- RESTful API — Mosque directory, search, prayer times, events, capacity, reviews, and more
- Real-time updates — Webhooks and push updates for prayer times and announcements
- Verified data — Official onboarding and mosque-claimed listings
- Rich data model — Capacity, facilities, accessibility, imams, Ramadan schedules, donations
- Developer-first — OpenAPI spec, comprehensive docs, and SDK-ready responses
| Package | Description |
|---|---|
| apps/api | REST API service (Node.js) |
| apps/docs | API documentation site |
| apps/landing | Marketing/landing page (mosque.api) |
| resources | Guides, use cases, pillar content, and developer resources |
- API Documentation — Endpoints, schemas, examples
- Getting Started — Keys, auth, first request
- Use Cases — Prayer apps, mosque finders, donations
- Resources — Integration guides, data model, SEO content
- Node.js 18+
- (Optional) Docker for running API and docs locally
# Clone the repo
git clone https://github.com/ummah-build/MosqueAPI.git
cd MosqueAPI
# Install all workspaces
npm install
# Run API (development)
npm run dev --workspace=apps/api
# Run API docs
npm run dev --workspace=apps/docs
# Run landing page
npm run dev --workspace=apps/landingSee each package’s README for more options (e.g. production build, env vars).
High-level roadmap and per-area tasks are tracked in:
- TODO.md — Master todo list and links to section-specific TODOs
Section-specific task lists:
- apps/api/TODO.md — API implementation
- apps/docs/TODO.md — Documentation
- apps/landing/TODO.md — Landing page & SEO
- resources/TODO.md — Guides and content
| Area | Endpoints |
|---|---|
| Core | GET/POST/PUT/DELETE /api/mosques, GET /api/mosques/{id} |
| Search | /api/mosques/search, /api/mosques/nearby, /api/mosques/filter |
| Prayer | /api/mosques/{id}/prayer-times, /api/mosques/{id}/jamaat-times |
| Events & Services | /api/mosques/{id}/events, /api/mosques/{id}/services |
| Imams & Leadership | /api/mosques/{id}/imams, /api/imams/{id} |
| Capacity & Attendance | /api/mosques/{id}/capacity, /api/mosques/{id}/attendance |
| Reviews & Ratings | /api/mosques/{id}/reviews, /api/mosques/{id}/ratings |
| Facilities | /api/mosques/{id}/facilities, /api/mosques/{id}/accessibility |
| Notifications | /api/mosques/{id}/subscribe, /api/mosques/{id}/announcements |
| Donations | /api/mosques/{id}/donation-info, /api/mosques/{id}/donations |
| Media | /api/mosques/{id}/photos, /api/mosques/{id}/videos, /api/mosques/{id}/floor-plan |
| Historical | /api/mosques/{id}/history, /api/mosques/{id}/architecture |
| Ramadan | /api/mosques/{id}/ramadan-schedule, /api/mosques/{id}/taraweeh-info |
| Webhooks | POST /api/webhooks/register, DELETE /api/webhooks/{id} |
| Verification | /api/mosques/{id}/claim, /api/mosques/{id}/verify |
Full reference: API Documentation.
- PRAYATTHEMosque.com — Find nearest mosque
- PRAYSAP.com — Accurate prayer times at mosques
- Mosque finder and building-planning apps
- Integration with Google Maps, Mapbox, and other map providers
- Women-focused mosque apps and women’s space discovery
- Donation platforms and mosque capacity visibility
- Archive of mosque database and lectures
- MuslimsInBritain.org — UK mosque directory
- Hartford Institute Mosque Database — US masjids
- Mawaqit — Prayer time displays (e.g. ~22k mosques in Europe)
- Mosqpedia — Mosque and architecture knowledge
- Wikipedia and other public lists for capacity and heritage data
- Secrets: Do not commit
.env,.env.local, or any file with API keys or passwords. They are in .gitignore. Use environment variables (e.g.NEXT_PUBLIC_API_URL,PORT) for config. - History: Repo history was rewritten to a single commit; no device paths (e.g.
/Users/...) or build artifacts (.next) are in the current commit. After pushing, usegit push --force origin mainso the remote matches.
If the repo history was rewritten to a single commit (e.g. to remove leaked paths), update the remote with:
git push --force origin mainMIT © ummah.build. See LICENSE.