Cannot access wordbyword audio of verses in client

[HelloCigar]

Do I still need to fetch and pass access tokens to access content resources like audio?

[basit3407]

@HelloCigar Thanks for reporting this.

If you're using the SDK, you should not need to fetch or pass the access token manually. The SDK handles token exchange and sends the token on content API requests for you.

Could you please explain the issue more clearly and, ideally, share a minimal reproducible example?

Please include:

• the exact SDK call you are making
• whether this is happening in a browser/client app or on the server
• the options you are passing
• the exact response or error you are getting
• what you expected to happen

Docs:
https://api-docs.quran.foundation/docs/sdk/javascript

[HelloCigar]

Hello. I am fetching from the backend(adonisjs) and passing the json to frontend. I wanted to play the audio from verses api, which has word by word translation and audioUrl(which is relative like '/wbw/0001_0002_0333.mp3). In the client/frontend, I use the browser Audio API like: const audio = new Audio(' https://apis.quran.foundation/content/api/v4/${audioUrl}) Well, I realized this wouldn't work as proxy is needed. But then I would need to build a stream on the backend like a route.get('/audio/') and send it to the frontend. Is there any guide on this? And what is the baseApi for audioUrl? It seems that Quran.com site itself use the quranic audio file which is 1 file per chapter and not the wbw audioUrl. Thank you

…

On Mon, Apr 13, 2026, 2:19 PM Basit Minhas ***@***.***> wrote: *basit3407* left a comment (quran/api-js#47) <#47 (comment)> @HelloCigar <https://github.com/HelloCigar> Thanks for reporting this. If you're using the SDK, you should not need to fetch or pass the access token manually. The SDK handles token exchange and sends the token on content API requests for you. Could you please explain the issue more clearly and, ideally, share a minimal reproducible example? Please include: - the exact SDK call you are making - whether this is happening in a browser/client app or on the server - the options you are passing - the exact response or error you are getting - what you expected to happen Docs: https://api-docs.quran.foundation/docs/sdk/javascript — Reply to this email directly, view it on GitHub <#47 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYAJ3CKW2MVFV6JUISAROUT4VSBI5AVCNFSM6AAAAACXVLXA3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMZUGI2DAOJWHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[basit3407]

Thanks, I reproduced the behavior.

Your understanding is correct: the relative word.audioUrl is not meant to be used as:

https://apis.quran.foundation/content/api/v4/${audioUrl}

That is not the correct playback URL for word-by-word audio.

For word-by-word pronunciation, quran.com uses the public audio CDN base instead:

https://audio.qurancdn.com/

So if the API gives you:

wbw/001_001_001.mp3

or

/wbw/001_001_001.mp3

you can play it in the browser as:

https://audio.qurancdn.com/wbw/001_001_001.mp3

In other words, you do not need to build a backend streaming route just to proxy the individual wbw mp3 files.

Separately, for full recitation playback with verse/word timing, quran.com uses the chapter audio endpoint plus timing segments, not the word-level audioUrl.

So the split is:

• word-by-word pronunciation: public CDN URL
• continuous recitation + highlighting: chapter audio endpoint

We would improve the docs here, since the current SDK/docs do not make this distinction clear enough.