Bring trusted Islamic source data into your website.

Apply for controlled API access to approved KitabGrid Quran and Hadith records, reviewed translations and licensed audio that is eligible for external reuse.

Approved-only dataDraft translations never leave the editorial workflow.

Source metadata includedLicence, attribution and provenance travel with the response.

Domain-bound accessBrowser credentials are restricted to the approved origin.

1. Contact and project

Contact name *

OrganisationOptional for personal/non-profit projects.

Website / project name *

Email *Verification and API decisions are sent here.

WhatsAppOptional. Used only if a review issue needs clarification.

2. Website binding

Main domain *Do not enter a page path. HTTPS is expected in production.

SubdomainOptional. If supplied, API access is bound to this exact host instead of the main domain.

3. Integration and expected usage

Integration type *

Expected API requests per day *

How will your website use the API? *

4. Requested data scopes

Quran textVerified Arabic ayahs and Surah metadata. Quran translationsOnly reviewed, approved translations for granted languages. Quran audioApproved reciters and ayah audio with source metadata. Hadith textPublished collections, Arabic text, numbering and grading metadata. Hadith translationsOnly independently approved/published translation versions. Hadith audioReturned only where approved narration audio exists.

Approval can grant fewer scopes than requested. Draft, rejected, hidden or licence-unapproved content is never returned.

5. Translation languages

6. Required acknowledgements

I accept the Developer API Terms, including key security, rate limits and acceptable-use rules. I have read the Privacy Policy and understand that application/contact data is processed to review and operate API access. I understand that Quran text, translations, Hadith, and audio may have different source licences. I will preserve required attribution/licence notices and will not claim rights that the API does not grant. I am authorised to request API access for the submitted domain/subdomain and will not use the credential on unrelated websites. I understand that access can be rate-limited, suspended, rotated or revoked for security, abuse, licensing, legal, technical or source-integrity reasons. Optional: send me occasional Developer API product updates. Transactional verification/security messages do not depend on this choice.

7. Security check

What is 8 + 6? *

After submission, verify your email. A staff member then reviews the domain, use case, requested scopes and source/licensing implications. Approval does not send a plaintext API key by email; you receive a short-lived one-time claim link.