JBou

//Authorization
{ ApiCommand.AuthorizationCodeFlow, new Uri("https://soundcloud.com/connect?scope=non-expiring&client_id={0}&response_type={1}&redirect_uri={2}") },
{ ApiCommand.UserAgentFlow,         new Uri("https://soundcloud.com/connect?client_id={0}&response_type=token&redirect_uri={1}") },
{ ApiCommand.UserCredentialsFlow,   new Uri("https://api.soundcloud.com/oauth2/token?client_id={0}&client_secret={1}&grant_type=password&username={2}&password={3}") },
{ ApiCommand.RefreshToken,          new Uri("https://api.soundcloud.com/oauth2/token?client_id={0}&client_secret={1}&grant_type=refresh_token&refresh_token={2}") },

//Me
{ ApiCommand.Me,                    new Uri("https://api.soundcloud.com/me.json") },
{ ApiCommand.MeTracks,              new Uri("https://api.soundcloud.com/me/tracks.json") },
{ ApiCommand.MeComments,            new Uri("https://api.soundcloud.com/me/comments.json") },

edwardaten

Example Partner API

Staging and Production Environments

Merchbar believes strongly in testing our integrations rigorously before enabling them on production data, so we ask that all of our partners set up a staging environment in addition to their production API servers.

The staging environment should service all of the same API requests as the production environment, with realistic-looking responses for each request that are consistent across calls. In cases where there would be real-world effects for API calls (e.g. shipping actual merchandise to a customer) those actions should not happen in the staging environment. In cases where the effects of real world actions would be necessary to completely simulate an API response (e.g. supplying the tracking number for an order) Merchbar recommends the staging environment supply a realistic-looking, but faked, response.

Security and Authentication