January 26, 2015 at 2:30 pm #369621 NextScripts.comParticipant That issue has been fixed in the API 2.1.5.63