Please tell us about yourself (include an email address):
Sipan hussein , an independent Kurdish app developer based in Iraq.
Email: sipankurdish09@gmail.com
I build and maintain "Hadith — فەرمودە", a free, non-commercial hadith reader for Kurdish speakers, currently being prepared for release on Google Play.
Your purpose in using this API:
I am publishing a free Android app that makes the nine canonical collections readable in Kurdish. Kurdish has two widely-written dialects — Sorani and Badini/Behdini — and neither has a hadith application with anything approaching full coverage, so most Kurdish readers currently access hadith only through Arabic or Turkish.
The app presents the Arabic text as the authoritative source, unaltered, with a Kurdish translation beside it. It covers all nine books — 429 chapters, roughly 41,000 hadiths — browsable by collection and chapter or by subject, with full-text search, bookmarks, the daily adhkar and the 99 names of God.
It is free, contains no advertising, and has no paid tier. I am currently reading the text from a public GitHub mirror of the hadith corpus, and would prefer to source it from sunnah.com so the app is built on the maintained, canonical dataset with proper attribution.
API rate limits:
Maximum requests per second: 5
Maximum requests per day: 5,000
These are deliberately modest because of how the app fetches. It requests one chapter at a time, only when a reader actually opens that chapter, and writes the result to the device's own storage permanently. A given installation therefore makes at most 429 requests over the entire lifetime of the app — one per chapter — and in practice far fewer, since most readers open a few dozen chapters at most. There is no background syncing, no prefetching and no polling.
Is your use case better served by an offline dump or programmatic API access?
An offline dump would suit this app better, and I would prefer it if one is available.
The app is designed to work without a connection: everything it fetches is cached to the device and re-read from disk afterwards, and readers in parts of Kurdistan have intermittent connectivity. A one-time snapshot would let me ship the corpus with the app so it works fully offline from first launch, and would remove essentially all recurring load on your servers.
API access would be a reasonable fallback if a dump is not available, but the dump is the better fit for both of us.
What are the languages in which would you like hadith data?
Arabic is the essential one — it is the authoritative text the app displays and the source everything else is derived from.
English as a secondary reference, used as supporting context for translation and to make chapter titles searchable for non-Arabic readers.
The Kurdish translations (Sorani and Badini) are produced on my side; I am not requesting Kurdish data from you. The app also offers a German interface, again translated on my side.
What programming language will your API client be in?
JavaScript — React Native (Expo SDK 53), running on the device. Requests are plain fetch calls over HTTPS from the client, with responses cached to local storage.
Please tell us about yourself (include an email address):
Sipan hussein , an independent Kurdish app developer based in Iraq.
Email: sipankurdish09@gmail.com
I build and maintain "Hadith — فەرمودە", a free, non-commercial hadith reader for Kurdish speakers, currently being prepared for release on Google Play.
Your purpose in using this API:
I am publishing a free Android app that makes the nine canonical collections readable in Kurdish. Kurdish has two widely-written dialects — Sorani and Badini/Behdini — and neither has a hadith application with anything approaching full coverage, so most Kurdish readers currently access hadith only through Arabic or Turkish.
The app presents the Arabic text as the authoritative source, unaltered, with a Kurdish translation beside it. It covers all nine books — 429 chapters, roughly 41,000 hadiths — browsable by collection and chapter or by subject, with full-text search, bookmarks, the daily adhkar and the 99 names of God.
It is free, contains no advertising, and has no paid tier. I am currently reading the text from a public GitHub mirror of the hadith corpus, and would prefer to source it from sunnah.com so the app is built on the maintained, canonical dataset with proper attribution.
API rate limits:
Maximum requests per second: 5
Maximum requests per day: 5,000
These are deliberately modest because of how the app fetches. It requests one chapter at a time, only when a reader actually opens that chapter, and writes the result to the device's own storage permanently. A given installation therefore makes at most 429 requests over the entire lifetime of the app — one per chapter — and in practice far fewer, since most readers open a few dozen chapters at most. There is no background syncing, no prefetching and no polling.
Is your use case better served by an offline dump or programmatic API access?
An offline dump would suit this app better, and I would prefer it if one is available.
The app is designed to work without a connection: everything it fetches is cached to the device and re-read from disk afterwards, and readers in parts of Kurdistan have intermittent connectivity. A one-time snapshot would let me ship the corpus with the app so it works fully offline from first launch, and would remove essentially all recurring load on your servers.
API access would be a reasonable fallback if a dump is not available, but the dump is the better fit for both of us.
What are the languages in which would you like hadith data?
Arabic is the essential one — it is the authoritative text the app displays and the source everything else is derived from.
English as a secondary reference, used as supporting context for translation and to make chapter titles searchable for non-Arabic readers.
The Kurdish translations (Sorani and Badini) are produced on my side; I am not requesting Kurdish data from you. The app also offers a German interface, again translated on my side.
What programming language will your API client be in?
JavaScript — React Native (Expo SDK 53), running on the device. Requests are plain fetch calls over HTTPS from the client, with responses cached to local storage.