REST Api Implementation won't work on Enterprise Edition of SalesForce

[wakurth]

When I call to get a token with the following format on my developer account, and another standard Salesforce account, I successfully get a token. I tried this on an Enterprise SalesForce account, and it's reply's with a 

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

grant_type=password&client_id={0}&client_secret={1}&username={2}&password={3}

Is there a difference is REST Api Calls being made to Enterprise SalesForce Accounts?

I did give an option to choose SalesForce version, but it's the same as my testing v24.0

Any help  or insight on this topic will be helpful.. Thanks!!!

[SimonF · Accepted solution]

EE includes the rest api and oauth support, what error do you get?

[wakurth]

The remote server returned an error: (400) Bad Request.

It's odd, because now it seems to work sometimes and not others... I am enabling some tracing to get more details.

It's good to know there's no difference in calls.

[SimonF]

A common problem that can cause issues like this is that you're not URLencoding the parameters correctly, then somestimes based on their values, you get away with it, and sometimes you dont.

[wakurth]

It ended up being a problem with caching in that browser... It worked on another machine, and then on the browser in question after a restart. All is well. Thank you.