Quickstart

The Itqan CMS API gives you authentic Quranic recitation data — reciters, recitations, riwayahs, qiraat, and ayah-level audio timings — from verified publishers, over a clean REST/JSON interface. No SDK, no setup: every endpoint is a plain GET you can run from a terminal right now.

Your first request

Time: ~30 seconds. Copy, paste, run — no API key required to read public content.

Base URL: https://staging.api.cms.itqan.dev

List the reciters available in the catalog:

curl

curl https://staging.api.cms.itqan.dev/reciters/

Python

import urllib.request
import json

with urllib.request.urlopen("https://staging.api.cms.itqan.dev/reciters/") as resp:
    data = json.load(resp)

print(f"Total reciters: {data['count']}")
for reciter in data["results"]:
    print(f"  {reciter['name']} — {reciter['recitations_count']} recitations")

JavaScript

const resp = await fetch("https://staging.api.cms.itqan.dev/reciters/");
const { count, results } = await resp.json();

console.log(`Total reciters: ${count}`);
results.forEach((r) => console.log(`  ${r.name} — ${r.recitations_count} recitations`));

Response:

{
  "count": 42,
  "results": [
    {
      "id": 1,
      "name": "Mishary Rashid Alafasy",
      "bio": "...",
      "recitations_count": 3
    }
  ]
}

That's a live integration. Want Arabic instead? Add -H "Accept-Language: ar" and every name, description, and bio comes back localized.

→ Full endpoint reference: List Reciters

Designed with care for developers

• Render from one request. Related resources are embedded as compact {id, name} objects, so a single response carries everything you need for a complete list item. → Related Resources
• One field, any language. Ask for Arabic or English with an Accept-Language header — the JSON keys never change, only the values. → Localization
• Stable, predictable shapes. Plural-noun paths, a consistent {count, results} envelope, and a unified error format make clients easy to write. → Design Principles
• Safe to build against. Resource IDs are stable integers and the API evolves additively — new fields never break existing integrations.

What's next

• API Reference — every endpoint, with interactive examples
• Design Principles — the conventions behind the API
• Error Handling — build resilient clients