You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please tell us about yourself (include an email address):
I am Mohammad Arshad Khan — mdarshadkhan1998@gmail.com. I'm an independent software developer building My Deen Guide, a free, offline-first Islamic companion mobile app (Flutter, Android/iOS) and its companion website (in Astro), grounded strictly in authentic Qur'an and Hadith under the guidance of Ahlus Sunnah wal Jama'ah scholars.
Your purpose in using this API:
My Deen Guide(mydeenguide.com - under development) displays authentic Dua's, hadith, and lot more to users with full provenance — collection, book/hadith number, and grading (Sahih/Hasan) — and never fabricates, paraphrases, or machine-translates sacred text. I would use Sunnah.com data to source verified hadith and their authentic translations for features such as authentic hadiths and searchable browsing by collection/reference. Every displayed hadith shows its grade, and nothing is altered. I would like both an API key and an offline dump: the offline dump to seed and bundle the verified hadith store for a lightweight, fully offline reading experience, and the API key for on-demand lookups/search of specific hadith and to keep content current over time.
API rate limits:
Maximum requests per second: 20
Maximum requests per day: 10000
(conservative estimate for development plus modest production traffic; happy to align with your policy)
Is your use case better served by having an offline dump of hadith data or programmatic API access?
I would require both, ideally. The offline dump is the better fit for our core architecture — the app is offline-first and bundles/caches verified hadith locally so users can read with no network, keeping the app lightweight. Alongside that, programmatic API access is useful for fetching specific hadith on demand and for refreshing/keeping content current. In short: the offline dump to seed the local verified store, and the API key for supplementary live lookups and updates.
What are the languages in which would you like hadith data?
Arabic (always shown, primary) and English (authentic translation) to start, then Urdu and additional authentic published translations as available. The app is multi-language, but we only display an authentic translation where a verified one exists (never machine-translated), falling back to English/Arabic otherwise.
What programming language will your API client be in?
Dart (Flutter) for the mobile app and JavaScript/TypeScript (Astro) for the website; hadith data is normalized and cached into a local SQLite (Drift) store on-device.
Please tell us about yourself (include an email address):
I am Mohammad Arshad Khan — mdarshadkhan1998@gmail.com. I'm an independent software developer building My Deen Guide, a free, offline-first Islamic companion mobile app (Flutter, Android/iOS) and its companion website (in Astro), grounded strictly in authentic Qur'an and Hadith under the guidance of Ahlus Sunnah wal Jama'ah scholars.
Your purpose in using this API:
My Deen Guide(mydeenguide.com - under development) displays authentic Dua's, hadith, and lot more to users with full provenance — collection, book/hadith number, and grading (Sahih/Hasan) — and never fabricates, paraphrases, or machine-translates sacred text. I would use Sunnah.com data to source verified hadith and their authentic translations for features such as authentic hadiths and searchable browsing by collection/reference. Every displayed hadith shows its grade, and nothing is altered. I would like both an API key and an offline dump: the offline dump to seed and bundle the verified hadith store for a lightweight, fully offline reading experience, and the API key for on-demand lookups/search of specific hadith and to keep content current over time.
API rate limits:
Maximum requests per second: 20
Maximum requests per day: 10000
(conservative estimate for development plus modest production traffic; happy to align with your policy)
Is your use case better served by having an offline dump of hadith data or programmatic API access?
I would require both, ideally. The offline dump is the better fit for our core architecture — the app is offline-first and bundles/caches verified hadith locally so users can read with no network, keeping the app lightweight. Alongside that, programmatic API access is useful for fetching specific hadith on demand and for refreshing/keeping content current. In short: the offline dump to seed the local verified store, and the API key for supplementary live lookups and updates.
What are the languages in which would you like hadith data?
Arabic (always shown, primary) and English (authentic translation) to start, then Urdu and additional authentic published translations as available. The app is multi-language, but we only display an authentic translation where a verified one exists (never machine-translated), falling back to English/Arabic otherwise.
What programming language will your API client be in?
Dart (Flutter) for the mobile app and JavaScript/TypeScript (Astro) for the website; hadith data is normalized and cached into a local SQLite (Drift) store on-device.