Get More Traffic

You've already got an audience that loves your content, product or service. Profit from helping them tell their friends and followers about you. The Universal Share API will enable the people that visit your website to share articles, comments, purchases and other activities from your website with their friends on multiple social networks. This API is free to use (premium upgrades are available), and helps you grow your bottom line and traffic without growing your marketing budget.

Universal Share API Documentation

Shareaholic provides social APIs to connect your site or application to each of the major social networks for sharing. If you can’t use the Shareaholic JavaScript SDK, you can link to these API endpoints directly. With these APIs you can customize the social sharing experience for your users to match the look and feel of your site or application.

Designed for Ease

All API methods are accessible via simple HTTP calls. We have optimized for ease of implementation, so you won’t see anything complicated. Most implementations of this API take less than 15 minutes to setup. Simply hit the provided URLs with their respective parameters, and you're done.

Getting Started: Authentication

All API endpoints require authentication credentials to be supplied as query arguments. To get started, you'll need a free Shareaholic account and Site ID. Signup for an account and then add your site to get your Site ID. The Site ID is your API Key.

Example:

...&apikey=8943b7fd64cd8b1770ff5affa9a9437b&...

Note: the apikey used in this document is intended for use as an example only. It is subject to change.

Share Content with over 100+ (and growing!) Destination Services

Let your users share content from any website, desktop app, mobile app, etc to any supported destination service.

Endpoint: https://www.shareaholic.com/api/share/?v=1

Working Example (posting a link to Facebook):

<a href="https://www.shareaholic.com/api/share/?v=1&apitype=1&apikey=8943b7fd64cd8b1770ff5affa9a9437b&service=5&title=What%20Do%20Your%20Customers%20Want%20to%20Buy%3F&link=https://nextviewventures.com/blog/what-do-your-customers-want-to-buy/&source=Shareaholic" target="_blank">Post to Facebook</a>

Give it a try: Post to Facebook

Notes:

• link, short_link, title, and notes parameters should be URL-encoded, plain text, no HTML, UTF-8. You can not include a parameter value in the request that has '&', '?', '#', ' ', or other reserved parameters without first encoding it.
• Parameters should not contain spaces: any parameter with spaces will be rejected. All spaces should be either percent encoded (%20) or plus encoded (+). Note that tabs, newlines and trailing spaces are all indications of errors. Please remember to strip leading and trailing whitespace from any user input before posting.
• Parameters must have a slash between the domain and the path component. For example, https://example.com?query=parameter is invalid, and instead should be formatted as https://example.com/?query=parameter
• link parameter value should be a complete URL and not a shortened link (like a bit.ly short link). You should always pass shortened links (ex. you may want to do this for Twitter) through the short_link parameter.
• templates[twitter][related] parameter value should be a valid Twitter handle, without the '@' or any whitespace. Multiple Twitter accounts can be added as a comma-separated list of values with no spaces in between.

Link Tracking & URL Shorteners

Shareaholic can automatically shorten the link for you using a supported shortening service that you specify.

...&shortener=bitly...

We currently support the following shorteners/parameter values:

You can further customize this option with your own bitly or j.mp account by setting the shortener_key parameter. If you set this parameter, the API will use your personal bitly generic access token to shorten the link.

...&shortener=bitly&shortener_key=9602e640dc831a9f32b68e570acffdbeccb1b760&...

For those of you that are using older versions of Bitly (where your token starts with "R_"), you will need to pass your Bitly username as well:

shortener_key format: username|R_token (i.e. delimited by "|").

Note that we only shorten links for services where it is appropriate (i.e. sharing to Twitter, but not Reddit). Also, if you would prefer not to publicize your shortener keys, you can setup your URL Shortener preferences and keys in your Shareaholic Admin Console. This is also the only way to setup a Bitly Custom Domain. If you do not pass the shortener and shortener_key parameters when calling the API call, the API will automatically lookup your saved cloud settings linked to your API Key, including the Bitly Custom Domain.

Templates i.e. customize your Tweets, Emails

By specifying a templates[][] API parameter, you can customize the default post format for services that support templates. Specifying a template is completely optional. The following services currently support templates:

• Twitter
• Email (also covers Gmail, Yahoo Mail, Outlook and AOL Mail)
• WhatsApp

The Share API supports a few different tokens in a template — you can use all, some, or none of them:

Sample template for Twitter:

...&templates[twitter][body]=Reading: ${title} (${short_link}) via @Shareaholic %23api %23devtools&...

Result:

Give it a try: Tweet this!

Suggested Twitter Accounts

By specifying the templates[twitter][related] API parameter, you can specify Twitter accounts to appear in the "Recommend Twitter Accounts" page that appears after a user shares your content via Twitter. This feature is currently available for Pro Subscribers only.

To specify Twitter accounts to be recommended, enter a comma-separated list of Twitter handles, omitting the '@' sign and any whitespace.

Sample templates[twitter][related] for Twitter:

...&templates[twitter][related]=my_twitter_handle,my_other_twitter...

Tags (describe your content)

Use the optional tags API parameter to further describe the content/URL being shared. Amongst many other benefits, you will get back more useful analytics tracking reports as a result.

tags takes a set of comma-separated values (CSV) with no trailing comma. Commas inside tag values MUST be URL encoded (as %2C) and commas separating tags MUST NOT be encoded. For example, the tags "python", "conference" and "Boston, MA" should be passed as:

...&tags=python,conference,boston%2Cma&...

You can pass in as many tags as you'd like, but we've found 3-5 to be most optimal.

Destination Services

Feedback

If you believe you have found a bug, or you’d like to request additional functionality, or you release something using this API, we’d love to hear from you.