Meet the new awe.sm for developers

15 views

Skip to first unread message

jere...@awe.sm

unread,

Dec 5, 2011, 5:43:38 PM12/5/11

to awesm-api

Hi, I'm Jeremiah, awe.sm's new developer experience lead.

Last week, we announced the latest release of the awe.sm platform
<http://awe.sm/5axrN>. Many of the things we've added are based
directly on your feedback. We can't wait to see what you'll build with
them.

New Developer Site
==================
<http://developers.awe.sm/> is the new home for the awe.sm developer
community. We've brought new documentation, tutorials, code samples,
and API references into one place.

Version 3 of our APIs
=====================
awe.sm now has more ways to share, track, retrieve stats, and manage
your projects. They're easier and faster to use than ever before.

We've added twelve new endpoints based on your feedback, one of which
is stats/active. This endpoint allows you to retrieve all-time stats
for recently clicked awe.sm links. If your app needs to track totals,
periodically use this endpoint to retrieve updated values. Check it
out at <http://developers.awe.sm/apis/stats-active/>.

If you're currently using version 2 of our APIs, now is a great time
to upgrade and take advantage of features like conversion tracking,
pivots, and expanded metadata. You can review all of the changes at
<http://developers.awe.sm/changelog/>.

New Demo Application
====================
We created <http://CuteOn.Me> for the TechCrunch Disrupt Hackathon and
have now open-sourced it. Cute On Me demonstrates how a real-world
application can use awe.sm's batch link creation, metadata
association, redirection patterns, conversion tracking, and advanced
stats retrieval. Fork the source and learn more at <http://
developers.awe.sm/solutions/cuteonme/>.

Talk to Us
==========
This is just the beginning! Our goal is to help you unlock social
media's full potential by putting data to work in interesting ways.

We're investing heavily in new new platform features and developer
tools for you. Your feedback helps us prioritize what we build next.
Respond here on the developer list, drop us a tweet @awesm, or email
<devel...@awe.sm>.