For launch, we built our own API. It's very simple. Post a JSON list of students with two attributes - the cumulative time they've spent on the program, and the

For launch, we built our own API. It's very simple. Post a JSON list of students with two attributes - the cumulative time they've spent on the program, and the cumulative "progress" they've made ("progress" metrics vary from application to application - things like "books read" or "lessons passed"). Full docs are here: https://dev.clever.com/docs/goals-api https://dev.clever.com/docs/goals-api The reasons we didn't adopt tincan/xAPI (or the very similar IMS Caliper standard) already are: 1. Limited K-12 adoption 2. Focus of existing standards on event transmission from "dumb" data senders (e.g. stateless content) to "smart" data hubs (e.g. LMSs that are the only source of analytics data). Our use case is different - as all of our data senders keep track of their own analytics, and it's critical for Goals to stay consistent with these systems. But now that we've launched & have a bit more time, I'd love to support an open standard. I'm optimistic that we can figure out a solution to #2, and then I'd love to have Clever drive K-12 adoption. In fact, I had a great call with IMS Global about this today :-)