I tested my app in the DE org and everything worked fine.  I went to connect it to our main org and I got this:

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

I know that our admins are going to resist enabling anything that they don't think is necessary for business.

Question:

1) Is there a doc somewhere on how to enable it properly?  (I couldn't find it)

2) Is there a doc from Salesforce that outlines the security best practices and soothes the mind of an average admin.  Things that I am looking for in a doc like that is that via Chatter API no one will be able to get the customer data, change the customer data, get any opportunity data or anything like that.

Thank you!!

Is there a way to pass in a non https URL for the OAuth?  Some development switch of some sort maybe?

The Chatter API Guide shows how to get authentication using grant_type = password.

I'd like to know how to set up the interactive flow.

The OAuth examples on Force.com look like they are not dealing with Chatter.  I tried posting:

client_id

client_secret

grant_type

redirect_uri

to 

https://na11.salesforce.com//services/oauth2/token

but I get an HTTP err 400 back.

The examples I see are posting to a whole different url: login.salesforce.com...

such as this example http://wiki.developerforce.com/index.php/Digging_Deeper_into_OAuth_2.0_on_Force.com

It looks a little suspicious.  In my mind changing from grant_type: password to something else should still post to the same URL.

What si the proper way to get an access token to Chatter REST API?

Is there a way to set up a scheduled class when a user installs my app?  I need to update SF objects based on statuses in an external service and I'd hate to put the user through a complicated setup.

Hey everyone!  I drive developer adoption of DocuSign API.  My team has been working very hard to put together some sample code and a walkthrough on how to integrate our web services into your native force.com apps.

NOW we have a free webinar where we will guide you through the process and answer any questions you might have.

If you were thinking about going completely paperless, this would be some really good info.

Below is the official marketing language:

Electronic signatures help your clients close transactions faster, reduce costs and streamline workflows.

This webinar will be a deep dive, showing you how to integrate the DocuSign API in your Salesforce.com solution.  We will review the DocuSign object model, API functions and a way to call DocuSign Web Services from ApexCode.  

At the end of the webinar you will know how to create a solution that sends a DocuSign envelope from any object in Salesforce.com with just one click.

Registration link: https://www1.gotomeeting.com/register/461739440

Is there a way to pass in a non https URL for the OAuth?  Some development switch of some sort maybe?

The Chatter API Guide shows how to get authentication using grant_type = password.

I'd like to know how to set up the interactive flow.

The OAuth examples on Force.com look like they are not dealing with Chatter.  I tried posting:

client_id

client_secret

grant_type

redirect_uri

to 

https://na11.salesforce.com//services/oauth2/token

but I get an HTTP err 400 back.

The examples I see are posting to a whole different url: login.salesforce.com...

such as this example http://wiki.developerforce.com/index.php/Digging_Deeper_into_OAuth_2.0_on_Force.com

It looks a little suspicious.  In my mind changing from grant_type: password to something else should still post to the same URL.

What si the proper way to get an access token to Chatter REST API?

I dont see VMforce server deployment in the latest Spring Tool suite.

Any help would be appreciated.

Thanks,

Yash