- Get Started
- Write Code
The Tin Can API (sometimes known as the Experience API or xAPI) is a brand new specification for learning technology that makes it possible to collect data about the wide range of experiences a person has (online and offline). This API captures data in a consistent format about a person or group’s activities from many technologies. Very different systems are able to securely communicate by capturing and sharing this stream of activities using Tin Can’s simple vocabulary.
Previous specifications were difficult and had limitations (see Tin Can vs SCORM), but the Tin Can API is simple and flexible. It lifts many of the older restrictions. Mobile learning, simulations, virtual worlds, serious games, real-world activities, experiential learning, social learning, offline learning, and collaborative learning are just some of the things that can now be recognized and communicated well with the Tin Can API.
It’s important to know that we don’t own the Tin Can API. ADL is the steward of the specification. We just know this space so well that ADL asked us to help develop it. The Tin Can API is community-driven, and free to implement.
And if you already know that you want to leverage the Tin Can API but need deeper technical assistance, our services group is here to help. Ask them anything. Really. You can also download the full Tin Can API specification here.
ADL, the keepers of SCORM, issued a BAA asking for ideas for the next generation of SCORM. We applied, and they asked us to research what the next-generation e-learning specification could/should look like. We then began gathering information about what the next evolution in the e-learning specification world should be in five main buckets:
We called this process Project Tin Can because it was meant to be a two-way conversation between us and the e-learning industry. It’s only fitting that the solution be named the Tin Can API – an elegant solution for letting learning systems communicate with one another. Check out a much more detailed explanation of Project Tin Can.
We not only realized the standard, we wrote it. Now that it’s in the community’s hands and actively developed by many developers and businesses, we are more engaged than ever. See the evolution of the Tin Can spec here.
We are helping people solve hard problems and working with the community to make the standard the best that it can be. Our minds are being blown daily, and we like it. We welcome the opportunity to make this better with you. If you have a question about Tin Can, we can help.
Want to find out more about Tin Can? Use the links below to dig deeper…
Or are you ready to move on and find out why you should adopt?