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):
Diliaver Akimov, akimov1995@gmail.com. I work on Arabic-to-English book
translation, with a semi-automated pipeline that assists human editors.
Your purpose in using this API:
Verification, not redistribution. When we translate a book that quotes
hadith, we need to check that the Arabic wording in our source corpus is
correct (it comes from OCR of printed books and can contain recognition
errors), and that the English rendering matches the hadith actually cited
rather than a similar one. Both checks are string comparisons against a
canonical reference. The hadith data is used inside our editorial tooling;
we do not republish your database or expose it as a service.
API rate limits:
Maximum requests per second: 10
Maximum requests per day: 2000
Is your use case better served by having an offline dump of hadith data or
programmatic API access?
An offline dump would suit us much better. Our verification runs over a whole
book at once and is entirely local, so batch lookups against a local copy are
both faster for us and far lighter on your servers than thousands of live
requests. If a dump is available, we would prefer it; API access as a fallback
for occasional individual lookups would still be welcome.
What are the languages in which would you like hadith data?
Arabic and English.
What programming language will your API client be in?
JavaScript (Node.js) for the pipeline, Python for the data preparation step.
Please tell us about yourself (include an email address):
Diliaver Akimov, akimov1995@gmail.com. I work on Arabic-to-English book
translation, with a semi-automated pipeline that assists human editors.
Your purpose in using this API:
Verification, not redistribution. When we translate a book that quotes
hadith, we need to check that the Arabic wording in our source corpus is
correct (it comes from OCR of printed books and can contain recognition
errors), and that the English rendering matches the hadith actually cited
rather than a similar one. Both checks are string comparisons against a
canonical reference. The hadith data is used inside our editorial tooling;
we do not republish your database or expose it as a service.
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 suit us much better. Our verification runs over a whole
book at once and is entirely local, so batch lookups against a local copy are
both faster for us and far lighter on your servers than thousands of live
requests. If a dump is available, we would prefer it; API access as a fallback
for occasional individual lookups would still be welcome.
What are the languages in which would you like hadith data?
Arabic and English.
What programming language will your API client be in?
JavaScript (Node.js) for the pipeline, Python for the data preparation step.