Every word on Buruja, as JSON.

Start here

Everything hangs off one base URL. Pin to /api/v1/ and the paths below will not move.

GET https://buruja.com/api/v1/index.json

That manifest lists every section, how many items it holds, and the URL shape to reach them. Each section then has an index.json (the list) and one file per item.

# list every companion
GET https://buruja.com/api/v1/companions/index.json

# then fetch one by its slug
GET https://buruja.com/api/v1/companions/bilal-ibn-rabah.json

# a day of The 365
GET https://buruja.com/api/v1/the-365/tazkiyah/index.json
GET https://buruja.com/api/v1/the-365/tazkiyah/002.json

# a whole surah, with Arabic, English and Swedish
GET https://buruja.com/api/v1/verses/2.json

Example

const BASE = "https://buruja.com/api/v1";

const list = await fetch(`${BASE}/companions/index.json`).then(r => r.json());

const first = await fetch(
  `${BASE}/companions/${list[0].slug}.json`
).then(r => r.json());

console.log(first.name);

Versioning & caching

• Pin to /api/v1/. Within v1, paths will not move and shapes will not change. New fields may be added, so parse leniently. A breaking change would ship as /api/v2/.
• /data/ serves the very same files, but it is the site's internal path and is free to change. Prefer /api/v1/ in anything you build.
• Responses are cacheable: max-age=300, s-maxage=3600, stale-while-revalidate=86400, with an ETag on every response for cheap conditional requests.
• Every section index is a JSON array, with one exception: hadith/riyad returns { books: [...] }.

Sections

19 sections, 1,962 indexed items (plus all 6,236 ayat of the Qur'an by surah).

Search

A prebuilt index of the whole site, if you want to add search to your own project.

GET https://buruja.com/api/v1/search-index.json