How do delete application

[Hugo Palma]

Hi,

i created an API application because i wanted to test a few things but now i want to delete it and can't really find a way to do it.

Any ideas ?

Thanks.

[Paul Mach]

Hi Hugo,

There is no way to delete an application from the website. It really doesn't hurt anything to keep it around unused. However, if you really want it removed, just send me your client_id. Let me know if you have other questions. 

Dr. Paul Mach

STRAVA

--
You received this message because you are subscribed to the Google Groups "Strava API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to strava-api+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Matt Pilott]

Paul please help me out, I wanted to delete my test api app (paceline) and create a new one, after removing the app from my apps i dont seem to be able to create a new app nor can i fully remove paceline from the "my api application" section. Can you please remove my app and tell me how i can create a new one.

client id: 5738

Thanks,

[Tim Blazina]

Hi Paul,

Following up on Hugo's question, is there any way to delete an app. I similarly made a test app but the scope for the application is not set correctly and I want to edit the scope by either deleting the test app or by creating a new one but there doesn't seem to be a way to do this on the website. How can this be done? Thanks!

Tim

[Dave Hughes]

Hi Tim,

I think you may be confused about scopes. In the API application settings, Strava does provide an authentication token as well as a refresh token, both of which have the read scope, but these are provided for convenience only, and I don't believe you ever have the opportunity to set a different scope for those.

There is no need to delete your API application in Strava settings, you can just change the settings at the bottom out of the API application settings page. But the scope is not set there, scope is specified by your application during the oauth authentication request.

Check out https://developers.strava.com/docs/authentication/#request-access

To summarize, you should:
1) Open in browser (be sure to use your API client ID): https://www.strava.com/oauth/authorize?redirect_uri=http://localhost:5744/&response_type=code&scope=read,read_all,activity:read,activity:read_all,profile:read_all&client_id=<YOUR CLIENT ID>

2) Strava will prompt for login and to authorize your application. After authorizing application, Strava will redirect your browser to the redirect_uri with some query params such as: http://localhost:5744/?state=&code=777595cceab06afad23ee9670bed5ca1ae2c4555&scope=read,read_all,activity:read,activity:read_all,profile:read_all

3) Assuming you don't have a server running on port 5744, your browser will fail to load that page. That's fine, because you just need to grab the query string's "code" parameter from the URL that your brother tried to visit. In the example given in step 2, the code is "777595cceab06afad23ee9670bed5ca1ae2c4555".

4) Now you need to exchange the code for an auth token. For this, you need to POST to https://www.strava.com/oauth/token with the code, as well as your API client ID and client secret. You can perform the POST with curl, HTTPie, or any other REST client.

POST https://www.strava.com/oauth/token?grant_type=authorization_code&client_id=<YOUR CLIENT ID>&client_secret=<YOUR CLIENT SECRET>&code=<CODE FROM STEP 2>

5) If all was successful, you will get a JSON response with access token, refresh token, and token expiry. The access token is used for your API requests (in the header "Authorization: Bearer <ACCESS TOKEN>"). If your access token expires, you must use the refresh token to retrieve a new one. That is similar to the request in step four, but with a couple different query parameters. You can refer to the documentation linked to above for more information on refreshing the access token.

Hope this helps you get started!
Dave

[Tim Blazina]

Hi Dave,

Thanks so much for the quick answer and the thorough explanation! It looks like I was indeed confused about scopes, I thought this was something defined upon  application creation. I had more or less figured out the steps you included here but didn't realize that you have to pass the 'code' returned by calling the oauth/authorize page as part of the post request to oauth/token. Everything is working fine now and I've been able to make some successful calls, thanks so much for the help.

As a side note, I think the answer you gave here about the authorization flow is much much clearer than what is currently written in the API docs, maybe you would consider including something similar in the docs. 

Thanks again!