My Quran Quest - Sources & Attribution

Resources used to build this app

This page summarizes the main external APIs, reference datasets, and recite attributions used in My Quran Quest. It focuses on the actual Quran, dua, grammar, and recitation sources behind the app.

APIs used

api.quran.com IndoPak Arabic ayah text, surah metadata, and recitation lookup.
api.alquran.cloud Surah list data plus English and Urdu translations used in recite mode.
verses.quran.com Arabic recite audio and word-by-word audio.
cdn.islamic.network English and Urdu recite audio URLs.
qutrub.arabeyes.org/api Arabic verb conjugation and form enrichment.

Data sources used

quranwbw.com/duas Source used for the dua dataset in the app.
quranic-corpus-morphology-0.4.txt Morphology corpus used in grammar and morphology features.
CAMeL Tools morphology database Local morphology analysis used during data building.

Translation and recitation attribution

Ayah pages - English translation Use en.sahih from AlQuran.Cloud. That is the Saheeh International translation used for the ayah pages.
Recite mode - English translation Uses en.asad from AlQuran.Cloud, which is Muhammad Asad's English translation for recite mode.
Urdu translation Both ayah pages and recite mode use ur.jalandhry from AlQuran.Cloud, referring to the Urdu translation by Fateh Muhammad Jalandhry.
Arabic recitation Uses the Alafasy recitation. Quran.com reciter 7 is Mishari Rashid al-Afasy, and AlQuran.Cloud also labels ar.alafasy as Alafasy.
Arabic text source The builder scripts pull IndoPak Arabic text from Quran.com's verse endpoint.

How recite data is built

Arabic text Fetched from api.quran.com using the IndoPak verse endpoint.
Urdu translation Fetched from api.alquran.cloud using ur.jalandhry.
English translation Fetched from api.alquran.cloud using en.asad, which is why recite mode differs from the ayah pages.
Audio Arabic audio comes from verses.quran.com, while English and Urdu audio use cdn.islamic.network patterns.