Skip to main content
Version: v4

Content APIs

Quran Foundation Content APIs offer programmatic access to the Quran's core content like chapters, verses, recitations, translations, and more, distinct from user-specific data like notes and bookmarks provided by User-related APIs.

Prelive Content API limitation

The prelive environment is for testing and development only. Its Quran content dataset includes only Al-Fatihah (surah 1) and Al-Baqarah (surah 2). Test content requests using these surahs. For the complete Quran dataset, use the production environment after production access is approved.

Integrity of Translations

Please disable any automatic browser-translation features (e.g. Google-Translate-in-Chrome) when displaying text returned by the Translations endpoints.
Re-translating an already vetted Quranic translation can introduce serious semantic errors.

How to get access​

We are using OAuth2 flows to authenticate and authorize requests. To get started, you need to get an access token to make requests to our APIs. Since the APIs are not user-related, you will need to use the client_credentials grant type and content scope when sending a request to The OAuth 2.0 Token Endpoint to get the access token.

After getting a valid access token, each request to get resources will have to include 2 headers mentioned below: x-auth-token and x-client-id. This spec also includes a small subset of Quran Reflect post-read endpoints that are compatible with the client_credentials grant. These operations still require x-auth-token and x-client-id, but they do not use the content scope. Use post.read for /quran-reflect/v1/posts/feed, /quran-reflect/v1/posts/{id}, and /quran-reflect/v1/posts/user-posts/{id}. Use comment.read for /quran-reflect/v1/posts/{id}/comments and /quran-reflect/v1/posts/{id}/all-comments. These are Quran Reflect gateway endpoints, not /content/api/v4/... endpoints. The Qira'at endpoints under /content/api/v4/qiraat/... are scope-gated: they require the qiraat.read scope (or the parent qiraat scope) instead of content, so request the Qira'at scope your client has been approved for when you get an access token.

Authentication​


The access token required for accessing the endpoints.

Security Scheme Type:apiKey
Header parameter name:x-auth-token