Sharing awe.sm Links

Client-side Sharing

This process is the most basic method of tracked sharing. The user clicks a link to share to a service. awe.sm will create a link and redirect the user to the service's sharing page and prefill the message area. This link demonstrates client-side sharing: it opens a new window on Twitter, offering to share this page with a unique awe.sm link. More examples.

	The url/share link creation endpoint is invoked client-side.
	An awe.sm link is created.
	The end user is redirected to a service-specific sharing destination with the new awe.sm link. This method does not allow for service-specific data (such as service post id, user audience size, etc) to be captured.

Server-side Sharing

Use this process when you have access to a service's API and the end-user has authenticated with you to post on their behalf. This process allows for capturing information about the post on the service and saving it back to the awe.sm link.

	An awe.sm link is created using the url endpoint.
	The link is presented to the user to curate a tweet.
	Your application calls the Twitter API to post the tweet on behalf of the user. Twitter responds to a successful update with a status object that contains information about the tweet and the user.
	Your application then updates the awe.sm link with the time the link was shared, the id of the tweet, the user’s Twitter id, and the number of people following the user by using the url/update/{awesm_id} endpoint.

Last updated 2011-10-28