How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Salesforce Sales Cloud Feeds API

Chatter feed operations

Salesforce Sales Cloud Feeds API is one of 52 APIs that Salesforce Sales Cloud publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Feeds. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a getting-started guide, a changelog, and an API reference.

This API exposes 2 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.1.0, at version 59.0.0.

Requests are made against a single base URL, https://{instance}.salesforce.com/services/data/v59.0/analytics.

2 operations 2 paths 6 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
59.0.0
Base URL
https://yourInstance.salesforce.com/services/data/v59.0
Authentication
OAuth 2.0, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 2

Salesforce Sales Cloud Feeds API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 1 scope. It accepts HTTP bearer tokens (OAuth 2.0 Access Token) (bearerAuth). By default, every request must be authenticated.

  • oauth2 — Salesforce OAuth 2.0 authentication

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Feeds 2

Chatter feed operations

GET
/chatter/feeds/news/me/feed-elements
Salesforce Sales Cloud Get news feed for current user
getNewsFeed 3 params → 200401
GET
/chatter/feeds/record/{recordId}/feed-elements
Salesforce Sales Cloud Get feed for a specific record
getRecordFeed 3 params → 200401404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are FeedElement (10 properties), UserSummary (8 properties), FeedElementPage (3 properties), ApiError (2 properties). Each schema is shown below with its type and property counts.

FeedElementPage
object
3 properties
FeedElement
object
10 properties
ErrorResponse
array
ApiError
object
2 properties
UserSummary
object
8 properties
MessageBody
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

salesforce-sales-cloud-feeds-api-openapi.yml Raw ↑

Other APIs Salesforce Sales Cloud publishes across the network.

Salesforce SOAP API
Metadata API
Streaming API
Platform Events API
Salesforce Composite API
Salesforce GraphQL API
Salesforce Pub/Sub API
Salesforce Sales Cloud Change Events API
Salesforce Sales Cloud Communities API
Salesforce Sales Cloud Completions API
Salesforce Sales Cloud Composite Batch API
Salesforce Sales Cloud Composite Graph API
Where this information came from

This is an independent, third-party profile of Salesforce Sales Cloud Feeds API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.