Chatter API

Chatter REST API

Overview

The Chatter REST API makes it easy to integrate mobile apps, intranet sites, and 3rd party web applications with Chatter. It provides resources for feeds, comments, likes, users, groups, private messages, and recommendations - using a REST-based API.  This page points to all Chatter REST API resources.

Getting Started

The Chatter API is available and default-on in all organizations and editions that have Chatter. If you're a developer you can sign up for a developer organization here to get started.

The Chatter API is designed for UI integration use cases like those listed above. If you are building a sync, analytics, archival or migration application, the sobject API is generally a better fit. See our Selecting Which API to Use page for more information.

API Documentation

  • Chatter API documentation: PDF | HTML

In the current doc, under /chatter/user/:user_id/ the follower, following, and group endpoints erroneously indicate that user id must be the context user. In fact user_id may be any user.

In the current documentation, the group element endpoint's myRole key is not completely described. The myRole key may have the following values: GroupOwner, GroupManager, StandardMember, NotAMemberPrivateRequested, NotAMember

For customers migrating from the Winter release, see the Spring '12 release notes for enhancements and changes: Spring '12 Release Notes. The Chatter API section begins on page 25.

Examples, Best Practices and Tips

Besides the documentation and articles, we're putting together a list of Examples, Best Practices and Tips.

Libraries and SDKs

Ruby/Rails gem for Chatter API and sobject REST API

Sample Applications

  • Rails + jQuery Mobile :- Sample implementation of a pure HTML5 Chatter client. Log in with any Force.com org credentials, and Try it out by logging in with your Force.com credentials, from any device, or grab the code to get a head start creating your own apps.

The below sample applications were created against an earlier version of the API, so many of the payload handling elements are now different. However they are good references for high level examples of how to query the API and authenticate. Please refer to the documentation and sample payloads for more information.

Other Documentation

OAuth is a prerequisite to using the API. The OAuth documentation is part of the help section inside your developer or production organization. Log in to your org, then click "help" in the upper right, and search for the following topics:

  • "Remote access" - This describes how you register an external application with Force.com. Once you've created a remote access application in your developer or production organization, users in any org may grant access to your application using OAuth.
  • "OAuth2" - This describes the various authentication flows that your application may use.
  • "Identity URLs" - After a user has authorized your application, your application can use the identity URL to get information about the authenticated user, including information like their name, their organization id, and their email.

Also see the Related Articles section on this page and the sample applications for more about OAuth and Authentication.

The Chatter API provides social and Chatter feeds related data. If your application needs access to other data, such as Accounts, Opportunities, Contacts and other objects, use the Force.com Web Services API.

Related Articles

Known Issues

Please see our Known Issues page.

Questions - Discussion Board

Post any questions you have to the Discussion Board.