Articulate's player.js seems to be intermittently not consuming our endpoint

May 18, 2017

This has been working fine for a few years now and just recently started intermittently failing.

We are using Articulate Storyline 2, exporting for TinCan.js.

Articulate is responsible for consuming our launch link, and extracting its endpoint for use in TinCan.

So if my launch link is :

<a href="story.html?endpoint="">Click!</a>

Then the Articulate LRS should be sending to ``.

Unfortunately, recently, this endpoint has been getting lost. And Articulate and only exports the endpoint into TinCan some of time. I get the same results in Scorm's cloud. Again, nothing has changed on our part to have caused this. It very strictly has to do with Articulate's processing of the endpoint and for some reason results in its failing.

We see failing requests like this : Same_Origin_No_Endpoint/undefinedactivities/state?method

Where it is both trying to send it to itself and not the endpoint, and producing an `undefinedactivities` line where that should be just `activities`. So clearly something within Articulate is not processing this information correctly.

Is there any way we could have access to your player.js file uncompiled, or to any developer documentation related to Articulate interaction with TinCan? There doesn't seem to be any information regarding the codebase of Articulate on this site.


1 Reply
Ashley Terwilliger-Pollard

Hi Trip,

Our Tin Can documentation is here. The following white paper provides technical information to help LMS developers implement the Tin Can API to fully support Articulate content.

And the following e-book, provided by, includes technical best practices for Tin Can API developers.

The underlying code base may be venturing into proprietary territory - but if you'd like to discuss your needs further, please feel free to connect with our Support team! 

This discussion is closed. You can start a new discussion or contact Articulate Support.