MuslimSalat APImuslimsalat.com ↗
Fetch Islamic prayer times for any location worldwide via the MuslimSalat API. Daily, weekly, monthly, and yearly schedules with qibla direction and 7 calculation methods.
What is the MuslimSalat API?
The MuslimSalat API gives access to Islamic prayer times for any city or location worldwide across 4 endpoints covering daily, weekly, monthly, and yearly schedules. The get_daily_prayer_times endpoint returns all six prayer times — fajr, shurooq, dhuhr, asr, maghrib, and isha — along with qibla direction, coordinates, and country data for a given location in a single call.
curl -X GET 'https://api.parse.bot/scraper/29204c39-375e-4028-899a-3f4e9148616b/get_daily_prayer_times?date=12-07-2026&method=egyptian&daylight=true&location=London' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace muslimsalat-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.muslim_salat_prayer_times_api import MuslimSalat, CalculationMethod
client = MuslimSalat()
# Get weekly prayer times for Mecca using Umm Al-Qura method
for day in client.prayerschedules.weekly(location="Mecca", method=CalculationMethod.UMM_AL_QURA):
print(day.date_for, day.fajr, day.maghrib)
# Get daily prayer times for London using MWL method
for day in client.prayerschedules.daily(location="London", method=CalculationMethod.MWL):
print(day.date_for, day.fajr, day.shurooq, day.dhuhr, day.asr, day.maghrib, day.isha)
Fetch a single day's prayer times for a given location. Returns fajr, shurooq, dhuhr, asr, maghrib, and isha times along with location metadata (coordinates, qibla direction, country). The calculation method defaults to the region's standard if omitted.
| Param | Type | Description |
|---|---|---|
| date | string | Date in DD-MM-YYYY format. Defaults to today. |
| method | string | Calculation method name or numeric 1-7. |
| daylight | string | Daylight saving adjustment: 'true' or 'false'. |
| locationrequired | string | City name or location (e.g. 'London', 'New York', 'Mecca'). |
{
"type": "object",
"fields": {
"for": "string, timeframe requested (daily)",
"items": "array of prayer time objects with date_for, fajr, shurooq, dhuhr, asr, maghrib, isha",
"query": "string, the location queried",
"method": "integer, calculation method code used",
"country": "string, country name",
"daylight": "string, daylight saving setting",
"latitude": "string, latitude of location",
"timezone": "string, timezone offset",
"longitude": "string, longitude of location",
"country_code": "string, ISO country code",
"qibla_direction": "string, qibla direction in degrees",
"prayer_method_name": "string, human-readable method name"
},
"sample": {
"data": {
"for": "daily",
"items": [
{
"asr": "5:21 pm",
"fajr": "2:12 am",
"isha": "11:47 pm",
"dhuhr": "12:59 pm",
"maghrib": "9:23 pm",
"shurooq": "4:36 am",
"date_for": "2026-6-10"
}
],
"query": "London",
"method": 5,
"country": "UK",
"daylight": "1",
"latitude": "51.508129",
"timezone": "0",
"longitude": "-0.128005",
"status_code": 1,
"country_code": "GB",
"status_valid": 1,
"qibla_direction": "119.04",
"prayer_method_name": "Muslim World League",
"status_description": "Success."
},
"status": "success"
}
}About the MuslimSalat API
What the API Returns
Each endpoint accepts a required location parameter (city name or place string such as 'Mecca' or 'New York') and returns an items array of prayer time objects. Every object includes date_for, fajr, shurooq, dhuhr, asr, maghrib, and isha fields. The daily endpoint additionally surfaces latitude, longitude, country, qibla_direction in degrees, and prayer_method_name alongside the numeric method code used for the calculation.
Calculation Methods
All four endpoints accept an optional method parameter. You can pass named strings (egyptian, shafi, hanafi, icna, mwl, umm_al_qura, fixed_isha) or numeric codes 1–7. The response echoes back both the integer method code and a human-readable prayer_method_name so callers can confirm which convention was applied. Daylight saving adjustments are controlled by the optional daylight parameter ('true' or 'false'), which is particularly relevant for European and North American locations during summer months.
Timeframe Endpoints
get_weekly_prayer_times returns 7 prayer time objects starting from the given date. get_monthly_prayer_times returns entries from the specified date through the end of that calendar month (up to roughly 31 objects). get_yearly_prayer_times covers from the given date to end of year, returning up to approximately 365 objects. All three endpoints share the same items array shape as the daily endpoint but omit location-level fields like qibla_direction and coordinates that are only present in the daily response.
Date and Location Handling
Dates are passed in DD-MM-YYYY format; if omitted, all endpoints default to the current date. The query field in the response reflects the location string as interpreted, and for indicates the timeframe served. Locations are resolved by name, so specificity matters for cities with common names — prefer 'Paris, France' over bare 'Paris' when precision is needed.
The MuslimSalat API is a managed, monitored endpoint for muslimsalat.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when muslimsalat.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official muslimsalat.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a prayer time widget for a mosque website that shows today's six prayer times using get_daily_prayer_times with a city parameter
- Generate a full-year prayer schedule PDF for distribution using get_yearly_prayer_times and iterating over the ~365 items array
- Display qibla_direction in degrees on a compass view using the field returned by get_daily_prayer_times
- Let users compare prayer times across different madhabs by switching the method parameter between hanafi, shafi, and mwl
- Integrate monthly prayer time tables into a Muslim calendar app using get_monthly_prayer_times with daylight saving toggled by region
- Send daily prayer time push notifications by calling get_daily_prayer_times each morning with a stored user location
- Populate a weekly schedule view in a mobile app using the 7-item array from get_weekly_prayer_times
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.