Assalamu Alaikum,
I'm building HadithIQ (sabeeljannah.com/apps/hadithiq), a hadith app for the Muslim community. I'd like to request an API key to access the Sunnah.com API.
Use case: Displaying hadith content with full sunnah.com references (including USC-MSA numbers) in our HadithIQ, with full attribution to sunnah.com.
App: HadithIQ, Developer: Sabeel Jannah Ltd (UK)
Website: I'd like to display the hadiths on the website in the Hadith Collection section on the HadithIQ landing page.
Your purpose in using this API:
We are building HadithIQ app — Read, study, reference, and memorise authentic Hadith in one beautiful app. HadithIQ brings the major collections together with faithful Arabic and English, an AI study assistant, smart search, memorisation plans, bookmarks, and full offline access — making the Sunnah simple, meaningful, and always within reach.
We want to use the sunnah.com API to:
Supplement our existing dataset with USC-MSA reference numbers (Vol./Book/Hadith), which our users frequently request and which are not available through any open dataset.
Ensure our hadith text, gradings, and metadata stay in sync with sunnah.com's manually verified, authoritative dataset.
All hadith content will be displayed with full attribution to sunnah.com.
API rate limits:
We are happy to work within whatever rate limits you set. Our sync process runs as an admin-triggered background job (not in real time), so we do not need high burst capacity — low sustained throughput is fine.
Maximum requests per second:
1–2 requests/second is sufficient for our sync use case.
Maximum requests per day:
During initial sync: up to ~5,000 requests/day (paginating through all collections once). During ongoing incremental sync: fewer than 100 requests/day.
Is your use case better served by having an offline dump of hadith data or programmatic API access?
An offline data dump would actually be ideal for our use case. Our sync process is a one-time bulk import followed by periodic delta updates — we don't need real-time API access. A dump (SQL, JSON, or CSV) would let us import the full dataset including USC-MSA references in a single operation and reduce ongoing API load on your servers. However, if a dump is not yet available, programmatic API access works well too.
What are the languages in which you would like hadith data?
Arabic and English. We currently display both scripts side by side in our browser UI.
What programming language will your API client be in?
TypeScript / Node.js (Express-based backend, running on a Linux server).
JazakAllah Khayran.
Salman Miah
info@sabeeljannah.com
Assalamu Alaikum,
I'm building HadithIQ (sabeeljannah.com/apps/hadithiq), a hadith app for the Muslim community. I'd like to request an API key to access the Sunnah.com API.
Use case: Displaying hadith content with full sunnah.com references (including USC-MSA numbers) in our HadithIQ, with full attribution to sunnah.com.
App: HadithIQ, Developer: Sabeel Jannah Ltd (UK)
Website: I'd like to display the hadiths on the website in the Hadith Collection section on the HadithIQ landing page.
Your purpose in using this API:
We are building HadithIQ app — Read, study, reference, and memorise authentic Hadith in one beautiful app. HadithIQ brings the major collections together with faithful Arabic and English, an AI study assistant, smart search, memorisation plans, bookmarks, and full offline access — making the Sunnah simple, meaningful, and always within reach.
We want to use the sunnah.com API to:
Supplement our existing dataset with USC-MSA reference numbers (Vol./Book/Hadith), which our users frequently request and which are not available through any open dataset.
Ensure our hadith text, gradings, and metadata stay in sync with sunnah.com's manually verified, authoritative dataset.
All hadith content will be displayed with full attribution to sunnah.com.
API rate limits:
We are happy to work within whatever rate limits you set. Our sync process runs as an admin-triggered background job (not in real time), so we do not need high burst capacity — low sustained throughput is fine.
Maximum requests per second:
1–2 requests/second is sufficient for our sync use case.
Maximum requests per day:
During initial sync: up to ~5,000 requests/day (paginating through all collections once). During ongoing incremental sync: fewer than 100 requests/day.
Is your use case better served by having an offline dump of hadith data or programmatic API access?
An offline data dump would actually be ideal for our use case. Our sync process is a one-time bulk import followed by periodic delta updates — we don't need real-time API access. A dump (SQL, JSON, or CSV) would let us import the full dataset including USC-MSA references in a single operation and reduce ongoing API load on your servers. However, if a dump is not yet available, programmatic API access works well too.
What are the languages in which you would like hadith data?
Arabic and English. We currently display both scripts side by side in our browser UI.
What programming language will your API client be in?
TypeScript / Node.js (Express-based backend, running on a Linux server).
JazakAllah Khayran.
Salman Miah
info@sabeeljannah.com