Content access and attribution
Public articles, clear references, and a stable link back to the original.
Read and discover
Article pages contain readable text and references without requiring JavaScript or an account for public stories. Find the complete collection in the article archive, canonical URLs in the sitemap, the latest 50 stories in the RSS feed, and a text index in llms.txt.
Read-only article API
Public article exports require no API key. Send a GET request to /api/public/articles/ARTICLE-SLUG for JSON, or append ?format=markdown for Markdown. These formats come from the same saved article as the reading page, retaining headings, lists, links, image credits and editorial disclosures.
Try the JSON example, its Markdown version, and the original article.
The JSON includes url (the canonical reading page), title, description, author, publisher, language, topic, publishedAt, modifiedAt, body.format, body.text, and article links. Links are references found in the text; their presence is not a claim that every linked page supports every statement. All dates use ISO 8601.
List articles and follow updates
Request /api/public/articles?limit=24 for metadata only. The default limit is 6; the maximum is 24. Use page=2 for the next page. Optional topic accepts a topic slug and author accepts a positive author ID. The response includes docs, hasNextPage, totalPages, and nextAfter.
For continuation pagination, pass the returned nextAfter.at as afterAt and nextAfter.id as afterId, URL-encoding both. Keep the same filters and limit. Continue while hasNextPage is true. Listing metadata does not unlock restricted article bodies.
Access boundaries and freshness
The full-text endpoint is available only for published public articles whose publication time has arrived. Unknown articles, drafts, scheduled stories, and account or member bodies return 404. Invalid formats or list parameters return 400. The endpoint accepts GET and HEAD; write methods are unsupported. Signing in does not unlock an export.
Exports are generated on request and use Cache-Control: no-store so corrected text and access changes are checked again. Their HTTP Link header identifies the canonical HTML page. Please fetch sequentially, avoid repeated bulk downloads, and retry temporary server failures with a delay.
Attribution, sourcing and reuse
When referring to an article, use its canonical URL, headline, stated author and publication date; record the modification date when it matters to your reference. Preserve the distinction between a Quran passage, a translation, a linked source, and the publication’s own explanation. Editorial desk bylines identify teams and do not imply individual scholarly qualifications.
Personal reflections and practical guides do not replace qualified religious instruction. Interpretive and doctrinal writing follows the review requirements in our editorial principles. Corrections and material relationships belong with the article, including in extracts.
Public access does not change copyright or grant a license to republish complete articles or remove credits. Share links and use lawful quotations with attribution under our terms. Requests for corrections or permissions can be made through Help.