I am brand new to SalesForce development, and want to explore the API and its capabilities. I have created a new Developer Edition account. I have not yet tried to access the API programmatically, but I am trying (unsuccessfully) to access it via both the Workbench ( https://workbench.developerforce.com/login.php ) and the Apigee Console ( https://apigee.com/console/salesforce ).
For some reason, in both cases I’m redirected to a URL with OAuth error code 1800 (e.g. https://na15.salesforce.com/setup/secur/RemoteAccessErrorPage.apexp?oauth_error_code=1800&display=popup in the Workbench case). At this URL, I am getting a screen with the text “Remote Access Authorization Error” – “There was a problem in setting up your remote access”. What am I doing wrong?
Some additional details:
- I can log into SalesForce just fine, the problem only occurs with API/OAuth access
- I have not touched anything in my brand-new Developer Edition account, except for (1) populating it with some sample data (Leads, Accounts, Contacts), and (2) resetting the security token (through “My Personal Information” -> “Reset My Security Token”)
- On the WorkBenh login screen, it does not matter which API version I choose (tried 24, 25 and 26), and I am using “Production” for the Environment since my login doesn’t seem to work at all for Pre-Release or Sandbox
(not a real answer, I expect to update it frequently as the situation develops)
Weird.
Yes, Developer Edition is a “Production” as far as connecting apps are concerned. You might have to file a Case with Salesforce Support (Help&Training link in the upper right corner).
Workbench does use API (and probably so does this Apigee thingie) but if you’re using your username & pass I don’t see how it might go to OAuth…
Can you download any other SF-related tooling (Data Loader, Force.com IDE, Real Force Explorer, Excel Connector, some iPad/Android app… hell, Chatter for Desktop even) and try the connectivity?
Sometimes API products don’t display special field for the security token (which you can bypass by entering longer string in the password field: “passwordSecurityToken”) but Workbench never asked for a token when I was accessing my Dev. Edition.