Apex Developer Guide

Apex Developer Guide
Getting Started with Apex
Writing Apex
Running Apex
Invoking Apex
Apex Transactions and Governor Limits
Using Salesforce Features with Apex
Actions
Approval Processing
Authentication
Chatter Answers and Ideas
Use Cases for the CommercePayments Namespace
Connect in Apex
Connect in Apex Examples
Connect in Apex Features
Working with Action Links
Working with Feeds and Feed Elements
Accessing ConnectApi Data in Experience Cloud Sites
Methods Available to Experience Cloud Guest Users
Using ConnectApi Input and Output Classes
Understanding Limits for ConnectApi Classes
Packaging ConnectApi Classes
Serializing and Deserializing ConnectApi Objects
ConnectApi Versioning and Equality Checking
Casting ConnectApi Objects
Wildcards
Testing ConnectApi Code
Differences Between ConnectApi Classes and Other Apex Classes
Moderate Chatter Private Messages with Triggers
Moderate Feed Items with Triggers
Experience Cloud Sites
Email
Metadata
Platform Cache
Salesforce Knowledge
Salesforce Files
Salesforce Connect
Salesforce Reports and Dashboards API via Apex
Salesforce Sites
Support Classes
Territory Management 2.0
Flows
Integration and Apex Utilities
Debugging, Testing, and Deploying Apex
Apex Language Reference
Appendices
Glossary
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Accessing ConnectApi Data in Experience Cloud Sites

Most ConnectApi methods work within the context of a single Experience Cloud site.

Many ConnectApi methods include communityId as the first argument. If you don’t have digital experiences enabled, use 'internal' or null for this argument.

If you have digital experiences enabled, the communityId argument specifies whether to execute a method in the context of the default Experience Cloud site (by specifying 'internal' or null) or in the context of a specific site (by specifying an ID). Any entity, such as a comment or a feed item, referred to by other arguments in the method must be located in the specified site. The ID is used in all URLs returned in the output.

Most URLs returned in ConnectApi output objects are Connect REST API resources.

If you specify an ID, URLs returned in the output use the following format:
1/connect/communities/communityId/resource
If you specify 'internal', URLs returned in the output use the same format:
1/connect/communities/internal/resource
If you specify null, URLs returned in the output use one of these formats:
1/chatter/resource
2
3/connect/resource