7

I'm Having trouble accessing the Chatter API in the context of a community. Mainly, we have a certain type of user that only has access as a user of a SalesForce community we are using to act as an Identity Provider.

We have enabled 'Allow API Access' on the user profile, and the community seems to have chatter enabled. However, calling an API endpoint like https://.force.com/services/data/v36.0/connect/communities/internal/chatter/users with a Bearer token returns the following

403: Forbidden 
{
  "message": "The Chatter Connect API is not enabled for this organization or user type."
  "errorCode": "API_DISABLED_FOR_ORG"
}

Does anyone have any ideas on what I could be missing

  • which edition is yours? – sfdcFanBoy Mar 2 '16 at 0:25
  • I am operating on a Full Copy sandbox of a Unlimited Edition organization. – David Staley Mar 2 '16 at 3:45
2
+50

See the documentation for Connecting to Salesforce Communities

You need to do the following, both when authenticating and accessing /chatter/users:

your communities custom domain name can be found by viewing the Communities Settings Page, which you can search for in the setup menu

  • this setting is only available in dev orgs according to sfdc support – Ralph Callaway Mar 4 '16 at 19:33
0

I don't know if this is the exact cause of the problem, but in /connect/communities/internal/chatter/users, "internal" needs to be replaced with the ID of the community the user belongs to. Using "internal" refers to the internal network, which your community user does not belong to.

Also, does GET /services/data/v36.0/connect/communities return the same HTTP 403 error?

  • /services/data/v36.0/connect/communities returns the same HTTP 403 error – David Staley Mar 8 '16 at 20:31
  • How about /services/data/v36.0/sobjects ? This will narrow down whether it's a general API problem, or a Connect API problem. – alouie Mar 9 '16 at 2:20
  • Strange, looks like the /services/data/v36.0/sobjects returns a invalid session 401 error. However, using the same bearer token for the /services/data/v36.0/connect/communities endpoint gives that 403 error. The OAuth2 token I am using is the one generated by Rails Omniauth's access code grant to the particular community. Note: the user that is logging in is an external identity user, could there be API limitations through that? Strangest of all, if I an enable the chatter tab for the community, I can manually edit their image and have that be returned during the Oauth2 exchange. – David Staley Mar 9 '16 at 16:58

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for?Browse other questions tagged or ask your own question.