-
Please tell us about yourself (include an email address):
We are volunteers maintaining a small, non-commercial community mosque website and app. You can reach us at prive.zakelijk1@gmail.com.
-
Your purpose in using this API:
We want to use authenticated hadith and supplication data from your collections across our mosque website and app, specifically:
a. A daily rotating hadith from Riyad as-Salihin and a daily supplication from Hisn al-Muslim, each shown with the exact Arabic text, English translation, grading, and source reference.
b. A searchable hadith archive for our community.
c. A planned "hadith of the day" notification — served from our own imported copy, not per-visitor calls.
d. Grounding our existing Islamic Q&A assistant in authenticated, source-cited hadith text so it references real narrations rather than generating them.
The data is imported once into our own database and served from there, so there are no per-visitor API calls. It matters greatly to us that the religious text is taken verbatim from an authenticated source such as yours rather than machine-generated. We keep the API key strictly server-side and never expose it in client-side or app calls.
-
API rate limits:
- Maximum requests per second: 2 is more than enough
- Maximum requests per day: Our real need is a one-time bulk import of a few dozen paginated requests, plus rare re-syncs, so any modest limit is fine.
-
Is your use case better served by having an offline dump of hadith data or programmatic API access?
An offline dump would be our preference — we import once and serve from our own database, and a complete local snapshot best serves the archive, search, and assistant-grounding use above. If you can provide a snapshot of Riyad as-Salihin and Hisn al-Muslim (Arabic + English + grades + references), that would be ideal. Programmatic API access for the initial import works equally well if a dump isn't convenient.
-
What are the languages in which would you like hadith data?
Arabic (original) and English (translation) and Dutch if available.
-
What programming language will your API client be in?
Node.js (JavaScript).
Please tell us about yourself (include an email address):
We are volunteers maintaining a small, non-commercial community mosque website and app. You can reach us at prive.zakelijk1@gmail.com.
Your purpose in using this API:
We want to use authenticated hadith and supplication data from your collections across our mosque website and app, specifically:
a. A daily rotating hadith from Riyad as-Salihin and a daily supplication from Hisn al-Muslim, each shown with the exact Arabic text, English translation, grading, and source reference.
b. A searchable hadith archive for our community.
c. A planned "hadith of the day" notification — served from our own imported copy, not per-visitor calls.
d. Grounding our existing Islamic Q&A assistant in authenticated, source-cited hadith text so it references real narrations rather than generating them.
The data is imported once into our own database and served from there, so there are no per-visitor API calls. It matters greatly to us that the religious text is taken verbatim from an authenticated source such as yours rather than machine-generated. We keep the API key strictly server-side and never expose it in client-side or app calls.
API rate limits:
Is your use case better served by having an offline dump of hadith data or programmatic API access?
An offline dump would be our preference — we import once and serve from our own database, and a complete local snapshot best serves the archive, search, and assistant-grounding use above. If you can provide a snapshot of Riyad as-Salihin and Hisn al-Muslim (Arabic + English + grades + references), that would be ideal. Programmatic API access for the initial import works equally well if a dump isn't convenient.
What are the languages in which would you like hadith data?
Arabic (original) and English (translation) and Dutch if available.
What programming language will your API client be in?
Node.js (JavaScript).