Discussions
- General Development
- Schema Development
- Apex Code Development
- Visualforce Development
- Formulas & Validation Rules
- Security
- Mobile
- Force.com Sites & Site.com
- Chatter Development
- Java Development
- .NET Development
- Perl, PHP, Python & Ruby
- Desktop Integration
- APIs and Integrations
- Visual Workflow
- Apple, Mac and OS X
- VB and Office Development
- AppExchange Directory & Packaging
- Salesforce Labs & Open Source Projects
- Other Salesforce Applications
- Jobs Board
- Force.com Discussion Boards
- :
- Developer Boards for Force.com and Database.com
- :
- APIs and Integration
- :
- Re: Setting up development environment for calling...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
Setting up developmen t environmen t for calling REST API
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
02-26-2012 10:39 AM
I am new to the Salesforce REST API (and Salesforce development in general), and I am working to set up my development environment for making/testing calls against the REST API.
In reading over the Getting Started with the Force.com REST API document, it appears that I need a public endpoint with an SSL certificate in place to even do the most basic development prototype (in order to do the OAuth step, which is of course a pre-requsite to all other calls).
Is that right? Is there no way to start developing and testing without setting up a publicly available web server with SSL in place?
Thanks much.
Solved! Go to Solution.
Re: Setting up developmen t environmen t for calling REST API
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
02-27-2012 12:53 PM
Hi ricb,
You can actually dispense with https if-and-only-if the server hostname is localhost, so URLs such as http://localhost:8443/RestTest/oauth/_callback will work just fine. This feature was added since that article was written; I'll go update the article right now...
(And localhost works fine for testing, since it's only the browser that needs to see it. And, if/when you want a public endpoint for testing, Heroku works really well for this, since Piggyback SSL is free).
Cheers,
Pat

