Al-Quran Cloud API

Name: Al-Quran Cloud API API
Brand: Al-Quran Cloud API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaContent Deliverynone23 EndpointsREST

For Agents

Read Quranic text, translations, transliterations, and audio recitations across multiple editions through 23 unauthenticated endpoints. Useful for agents building study tools, reading apps, or daily-verse delivery.

Quickstart

Get started with Al-Quran Cloud API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get an ayah of the Quran by reference"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Al-Quran Cloud API API.

Retrieve a full surah by number with the original Arabic and any chosen edition

Get a single ayah by reference (e.g., 2:255) in the original or a translation

Pull divisions of the Quran by juz, manzil, ruku, page, or hizb quarter

List all sajda ayahs from a specified edition

GET STARTED

Start building with Al-Quran Cloud API API

Explore with Jentic

View OpenAPI Document

Use for: Get the text of Surah Al-Fatiha in English, Retrieve Ayat al-Kursi with an English translation, Find every ayah that contains the word 'mercy', Get the audio recitation of Surah Yasin by Abdul Basit

Not supported: Does not host hadith collections, generate AI translations, or provide tafsir commentary — use only for retrieving Quran text, audio editions, and divisions.

Jentic publishes the only available OpenAPI document for Al-Quran Cloud API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Al-Quran Cloud API, keeping it validated and agent-ready. The Al-Quran Cloud API serves the full text of the Holy Quran along with translations, transliterations, and audio recitations across many editions and languages. Its 23 endpoints support retrieval by surah, ayah, juz, manzil, ruku, page, hizb quarter, and sajda, plus keyword search and metadata. The API is open and unauthenticated, making it well suited to mobile apps, study tools, and reading-plan integrations.

Use Cases

Patterns agents use Al-Quran Cloud API API for, with concrete tasks.

★ Daily Verse and Reading Plan Apps

Mobile app developers wire daily-verse and structured reading-plan features off the juz, page, and ayah endpoints. The API serves both Arabic and a chosen translation in one response, so the app can show the original text and its translation side by side without managing the corpus locally.

Call GET /juz/1/quran-uthmani and GET /juz/1/en.sahih in parallel, then assemble each ayah pair into the day's reading plan view.

Quran Study and Search Tools

Study platforms expose keyword search across the original Arabic and translation editions through the /search endpoint, then deep-link results back to the surah/ayah views. Because the API exposes editions for transliteration and translations, the same study session can show meaning, pronunciation, and original text together.

Call GET /search with keyword 'mercy' and edition en.sahih, take the first result's surah and ayah, and call GET /ayah/{reference}/quran-uthmani to retrieve the original Arabic.

Audio Recitation Playback

Listen-along players use the audio editions surfaced by the API to stream recitations by reciter, surah, or ayah. The /edition endpoint lists the available recitation editions, and the surah/ayah endpoints in those editions return URLs to the audio assets, so a player can build a reciter picker without bundling audio metadata locally.

Call GET /edition?format=audio to list available reciters, then GET /surah/36/ar.alafasy to retrieve the audio URL for Surah Yasin.

AI Agent Quran Lookups via Jentic

An AI agent built on Jentic can field questions like 'show me Ayat al-Kursi in English with the Arabic' and resolve them to the right ayah-by-reference call without manual URL construction. Because the API is unauthenticated, no credentials are needed; Jentic still routes the request through its standard execution layer for logging and retries.

Search Jentic for 'get an ayah by reference', load the /ayah/{reference}/{edition} schema, and execute it twice for reference 2:255 with editions quran-uthmani and en.sahih.

Key Endpoints

23 endpoints — jentic publishes the only available openapi specification for al-quran cloud api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/surah

List all surahs

GET

/surah/{number}/{edition}

Get a surah in a specific edition

GET

/ayah/{reference}/{edition}

Get an ayah by reference in a chosen edition

GET

/juz/{number}/{edition}

Get a juz in a chosen edition

GET

/page/{number}

Get a Quran page by number

GET

/search

Search the Quran text and translations

GET

/edition

List available text and audio editions

GET

/meta

Get Quran metadata (counts of surahs, juzs, pages, etc.)

GET

/surah

List all surahs

GET

/surah/{number}/{edition}

Get a surah in a specific edition

GET

/ayah/{reference}/{edition}

Get an ayah by reference in a chosen edition

GET

/juz/{number}/{edition}

Get a juz in a chosen edition

GET

/page/{number}

Get a Quran page by number

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Al-Quran Cloud is unauthenticated, so no credentials are stored in the MAXsystem vault for this API. Jentic still mediates the request, isolating the agent from network and retry concerns.

Intent-based discovery

Agents search Jentic with intents like 'get an ayah by reference' or 'list Quran translation editions' and receive the matching operation schema directly, ready to call without consulting the docs.

Time to first call

Direct integration: a few hours to learn the reference format and edition catalogue. Through Jentic: under 30 minutes to search, load, and execute the first ayah lookup.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Quran.com API

Quran.com's API exposes the same corpus with richer tafsir and word-level data

Choose Quran.com when the workflow needs tafsir, word-by-word translation, or per-word audio rather than ayah-level retrieval.

Complementary

OpenAI API

Generate explanations or summaries of retrieved ayahs through a language model

Use OpenAI alongside Al-Quran Cloud when the agent needs to summarise or contextualise retrieved verses for a study app.

Complementary

Cloudinary Upload API

Optimise and serve recitation audio assets from a CDN-backed media platform

Use Cloudinary when an app wants to cache, transcode, or serve Al-Quran Cloud audio through a managed CDN.

FAQs

Specific to using Al-Quran Cloud API API through Jentic.

Why is there no official OpenAPI spec for Al-Quran Cloud API?

Al-Quran Cloud does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Al-Quran Cloud API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Al-Quran Cloud API use?

None. The API is fully open and does not require an API key, OAuth token, or sign-up. Through Jentic the call is still routed through the standard execution layer for retry handling and logging.

Can I retrieve a single ayah with translation using the Al-Quran Cloud API?

Yes. Call GET /ayah/2:255/en.sahih for a translated ayah by reference, and GET /ayah/2:255/quran-uthmani in parallel for the original Arabic. The reference format is surah:ayah.

What are the rate limits for the Al-Quran Cloud API?

The API does not publish hard per-key rate limits because it is unauthenticated, but it is community-funded — keep request volume reasonable, cache aggressively at edge or app level, and retry with backoff on 429 or 5xx responses.

How do I look up Ayat al-Kursi through Jentic?

Search Jentic for 'get an ayah by reference', load the /ayah/{reference}/{edition} schema, and execute with reference=2:255 and edition=en.sahih. No credentials are needed; Jentic still wraps the call for retries.

Does the Al-Quran Cloud API serve audio recitations?

Yes. Call GET /edition with format=audio to list reciter editions, then GET /surah/{number}/{edition} (e.g., ar.alafasy) to retrieve URLs to the audio assets for that surah.