-
Please tell us about yourself (include an email address):
My name is Salman Mubashir. My contact email is saiman.mubasher@gmail.com
-
Your purpose in using this API:
I am engineering DALIL, a source-driven Islamic chatbot designed for a large-scale community. Our hadith subsystem requires highly structured, semantic retrieval. We are building a "Baab-Enriched Retrieval" architecture that uses OpenSearch vector embeddings to map user intent to specific hadith. To achieve high precision (especially for Akhlaq vs. Eschatology queries), we rely heavily on the granular metadata of Imam al-Bukhari's taxonomy—specifically the exact mapping of the Matn to its parent Kitab and Baab (Tarjamah). We are requesting access to ensure our canonical PostgreSQL database is seeded with the most accurate and structurally complete text available.
-
API rate limits:
Maximum requests per second: 5 req/s (primarily for controlled ingestion/syncing scripts, not live user traffic).
Maximum requests per day: 1,000 req/day.
-
Is your use case better served by having an offline dump of hadith data or programmatic API access?
An offline dump is vastly superior for our architecture. Because our system generates semantic embeddings (combining the Book, Chapter Heading, and Text into a single vector) for our search cluster, having a complete, relational offline snapshot (e.g., a .sql or .sqlite dump) is our primary requirement. It allows us to build our ingestion pipelines and vector targets deterministically without hitting network bottlenecks or scraping API endpoints.
-
What are the languages in which would you like hadith data?
Arabic and English. We strictly require both languages not just for the Matn (text), but crucially for the Kutub (Books) and Abwab / Tarajim (Chapter Headings) metadata.
-
What programming language will your API client be in?
Python (for our ETL, ingestion pipelines, and OpenSearch embedding builders) and [Insert Backend Language, e.g., TypeScript/Node.js or Python/FastAPI] for our live application backend.
Any Help will be greatly appreciated. JazakAllahhu Khairan
Please tell us about yourself (include an email address):
My name is Salman Mubashir. My contact email is saiman.mubasher@gmail.com
Your purpose in using this API:
I am engineering DALIL, a source-driven Islamic chatbot designed for a large-scale community. Our hadith subsystem requires highly structured, semantic retrieval. We are building a "Baab-Enriched Retrieval" architecture that uses OpenSearch vector embeddings to map user intent to specific hadith. To achieve high precision (especially for Akhlaq vs. Eschatology queries), we rely heavily on the granular metadata of Imam al-Bukhari's taxonomy—specifically the exact mapping of the Matn to its parent Kitab and Baab (Tarjamah). We are requesting access to ensure our canonical PostgreSQL database is seeded with the most accurate and structurally complete text available.
API rate limits:
Maximum requests per second: 5 req/s (primarily for controlled ingestion/syncing scripts, not live user traffic).
Maximum requests per day: 1,000 req/day.
Is your use case better served by having an offline dump of hadith data or programmatic API access?
An offline dump is vastly superior for our architecture. Because our system generates semantic embeddings (combining the Book, Chapter Heading, and Text into a single vector) for our search cluster, having a complete, relational offline snapshot (e.g., a .sql or .sqlite dump) is our primary requirement. It allows us to build our ingestion pipelines and vector targets deterministically without hitting network bottlenecks or scraping API endpoints.
What are the languages in which would you like hadith data?
Arabic and English. We strictly require both languages not just for the Matn (text), but crucially for the Kutub (Books) and Abwab / Tarajim (Chapter Headings) metadata.
What programming language will your API client be in?
Python (for our ETL, ingestion pipelines, and OpenSearch embedding builders) and [Insert Backend Language, e.g., TypeScript/Node.js or Python/FastAPI] for our live application backend.
Any Help will be greatly appreciated. JazakAllahhu Khairan