Request for API access: [Your Name]

[fushi02]

• Please tell us about yourself :

Ibrahim mohamed and my email is [email protected]

• Your purpose in using this API:

I plan to use it in my website and probably an app i will make in the future

• API rate limits:
  • Maximum requests per second:
  • Maximum requests per day: Maximum requests per second: 5-10 requests/second (to avoid being throttled by most APIs).

Maximum requests per day: 1,000-10,000 requests/day (depends on API provider

• Is your use case better served by having an offline dump of hadith data or programmatic API access?

Real-time Data – Ensures we always display the latest translations, recitations, and tafsir without manual updates.

Dynamic Features – Supports user interactions (search, bookmarks, random verses/hadith) that require live fetching.

Scalability – Avoids hosting large datasets ourselves, reducing storage and maintenance overhead.

Ease of Implementation – Faster to deploy using existing APIs (e.g., Al-Quran Cloud, Sunnah.com) rather than managing offline data.

Exception: If we later need guaranteed uptime or face API rate limits, we’ll supplement with cached offline dumps (e.g., preloaded JSON for static content).

Preferred Solution: Start with APIs + client-side caching, then optimize as needed.

• What are the languages in which would you like hadith data?

For our Hadith website, we prioritize the following languages:

Primary Languages (Essential): Arabic (Original text – mandatory for authenticity)

English (Widest reach – e.g., Sahih Bukhari, Sahih Muslim translations)

Secondary Languages (Important for Global Users): Urdu (Major Muslim demographic)

Indonesian/Malay (Large user base in Southeast Asia)

French/Spanish (For European/African audiences)

Optional (If Available): Turkish

Bengali

Swahili

somali

• What programming language will your API client be in?

for our Quran/Hadith integration, we'll be using:

Primary Language: JavaScript (Node.js for backend, React/Vue for frontend)

Key Reasons:

Full-stack consistency - Using JS across frontend and backend simplifies development

Modern web compatibility - All major browsers support our chosen approach

Rich ecosystem - Access to libraries like Axios for API calls and Next.js for SSR