When to Use Connect REST API

Is Connect REST API the right API for you?

Use Connect REST API to:

  • Build a mobile app.
  • Integrate a third-party web application with Salesforce so it can notify groups of users about events.
  • Display a feed on an external system, such as an intranet site, after users are authenticated.
  • Make feeds actionable and integrated with third-party sites. For example, an app that posts a Chatter item to X (formerly Twitter) whenever the post includes #tweet hashtag.
  • Create simple games that interact with the feed for notifications.
  • Creating a custom, branded skin for Chatter for your organization.

How Is Connect REST API Different from Other Salesforce APIs?

Connect REST API differs from REST API in multiple ways, including:

  • Data is structured for rendering on websites and mobile devices.
  • Returned information is localized to the user’s time zone and language.
  • Changed values that are tracked in a feed are returned as value-pair representations.
  • Rate limiting for Chatter REST API resources (a subset of Connect REST API resources) is per user, per application, per hour. The documentation for every Chatter resource specifies that Chatter is required. Requests to resources that don’t require Chatter count toward the Salesforce Platform total API request allocations, which are per org and span a 24-hour period.

If needed, extract an ID from REST API and use it in requests to Connect REST API.

Connect in Apex

Many Connect REST API resource actions are exposed as static methods on Apex classes in the ConnectApi namespace. This namespace is also referred to as Connect in Apex. Use Connect in Apex to develop applications on the Lightning Platform without using HTTP callouts from Apex.

The documentation for Connect in Apex is available in the Apex Developer Guide and the Apex Reference Guide.