Hmm there should be, since its using REST-WS.
But another question:
Did you try the serialized session aswell?
I would do it like this:
1. Try sending the URL without the token - if you receive a promtp - you should be fine.
-> if not - Problem is the Token
2. Try using the serialized session - if it works -decide wether to use sS or figure out the token problem.
3. Analyse the token problem. Since the token is using an additional licence, you should be able to verify the token ID - or even get the encoded URL.
Let me know.
Cheers,.