Feedback requested: http://developers.strava.com

[Mateo Ortega]

Strava Developers, 

We need your feedback, We're working on consolidating a few sources of Strava API information and mixing in a new awesome one.

Basically 

strava.github.io/api + labs.strava.com/developers + swagger.io = http://developers.strava.com

Please check out http://developers.strava.com and let us know what you think. Don't be shy. We want to know what is good, what is bad and what we need to add. Plese, respond on list or to me personally.

Thanks in advance!

PS check out https://medium.com/strava-engineering/enabling-integration-collaboration-and-innovation-with-the-strava-api-9d2c03f9dffa while you're at it.

Mateo

--

Mateo A. Ortega

STRAVA

Head of Integration

[Martin T]

Fantastic work Mateo (and the team).  

A huge improvement over the documentation that is currently in place.

I specifically love the API Documentation with code fragments in multiple languages.  That will save new developers a heap of time.

Good to see the fuller description of the OAuth flow.  For many new developers that is the hardest part to understand and get working.

Cheers,

MartinT

KOM Defender Developer 

[Justin Zimmerman]

Thanks for your hard work Mateo! It looks great.

Just as a note, if Martin wouldn't have said something about the authentication docs I wouldn't have found them hidden inside the top drop down. Seconding that authentication is the most difficult part of working with the Strava API, it might make sense to have it in a more prominent location.

Best,

Justin

[Mateo Ortega]

Good feedback so far...thanks! 

One question on the Client Libraries, what languages would you all like to see? Or since these are Swagger generated, should we just hand out the definition & instructions and be done with? In any case, the definition will be available, just a question on whether it's worth doing the client generation for developers.

Mateo

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Sam Sandberg]

Very exciting indeed, congrats!

A few thoughts:

Have you considered open sourcing this website? It might be a good way of filling in some remaining blanks and allowing us devs an easy way to follow along (this brings to mind some previous posts about it being nice that there's a changelog but not having a good way of getting updates for when it is modified).

I don't know much (anything) about Swagger, but I am a bit curious about the client libs/code samples.

Specifically:

1. I know `HTTPie` is popular (maybe?), but everyone knows/has `curl`. Why get rid of it?

2. I see the language-specific dropdowns, but they appear to be using client libs. Maybe list those somewhere? In particular:

- Java has `import com.strava.api.v3.api.ActivitiesApi`

- ObjC has `STRVActivitiesApi`

- JavaScript has `var StravaApiV3 = require('strava_api_v3');`

- C# has `using com.strava.api.v3.Api;`

- Python has `import swagger_client` - what even is that?! How about using hozn's elaborate python client: https://github.com/hozn/stravalib

Re: the Authentication page, it might be helpful to have some content dedicated to client-specific auth (Android/iOS/etc.) - maybe citing examples or projects like this: https://github.com/loisaidasam/strava-authenticator-android (full disclosure, I wrote this one).

Anyway, keep up the great work!

Best,

-Sam

Sam Sandberg


"When you know the notes to sing, you can sing most anything"

[Justin Zimmerman]

I'd love to see Go on the swagger doc, since it's the only "official" supported strava library :) but to second Sam, I would be happy to help keep documentation updated if it was open sourced.

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.

[Tim Heuer]

Feedback:

Good changes here, thanks.  One thing I think you can expand on in "Learn" is providing more scenario-focused examples.  As someone that works on API docs for a living, this is the most valuable to our customers, not the individual POST/GET call.  I think showing a canonical app of authorizing, listing friends, posting a ride in a way would be good...put it on GitHub, done.  Of course you'll have to pick a language, but I think Swift would be a good one.

Client Libraries:

Yes, these are needed.  These accelerate app development for sure.  I'd like to see Swift, C#, Go and Python.

-th

-------
http://timheuer.com/blog/
twitter: @timheuer

To unsubscribe from this group and stop receiving emails from it, send an email to strava-api+unsubscribe@googlegroups.com.

[Mateo Ortega]

I will try and summarize and answer in one email.

-We do plan on githubbing the docs

-Seems like Client Libraries in addition to the definition would be helpful. Languages requested so far are: Swift, C#, Go and Python. Any language that is referenced in the docs should probably be available as a client library.

-Will look into adding curl to the examples. I personally use curl or postmates, never touched HTTPie altough it does look really cool.

-Give some special callout to the OAuth material

-Show some real world scenario recipe type examples

Let me know if I missed anything.

Also, if anybody wants to have a go at the swagger def or a particular client library let me know offlist. 

Mateo

[Pavlo Ivanchyshyn]

Where is an information about web hooks subscriptions? Or it's not just migrated?

[Mateo Ortega]

Pavlo,

That is correct. There are a few things in the old docs that we need to find places for. Changelog, file format specifics....

Mateo

--

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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Klaasjan M.]

Hi Mateo,

I love the pages with all the documentation.

I develop in vb.net and c#. I want to use com.strava.api.v3.Api, but i cannot find it on the site to download the api.

Can you tell me how to do it?

Thanks.

Klaasjan

Op donderdag 31 augustus 2017 01:18:31 UTC+2 schreef Mateo Ortega:

[Tim Heuer]

Klaasjan,

You would use the instructions on the developer page to generate the C# (VB not supported as a lang output) code for the api/client using swagger-codegen.

Command would be: 

$ swagger-codegen generate -i https://developers.strava.com/swagger/swagger.json -l csharp-dotnet2 -o generated/csharp

-------
http://timheuer.com/blog/
@timheuer

[Klaasjan M.]

Hi Tim,

Thanks for your help, but i got errors (i used https://editor.swagger.io/) and loaded the json file.

But i was enable to create c# code. But in visual studio i got 33 errors concerning the enum of activities.

Are you familiar with these type of errors.

Regards

Klaasjan

Op zondag 25 november 2018 16:28:01 UTC+1 schreef Tim Heuer:

[Klaasjan M.]

Hi,

I was able to build the DDL. i was only expected a dll with a name like com.strava.api.v3.dll. But i get a dll called IO.Swagger.dll.

I'm new to swagger. Did i something wrong?

or is de io.swagger.dll the correct one to use in my software to interact with Strava.

Best Regards,

Klaasjan

[Tim Heuer]

That’s an input parameter you can put in config.json for the package name. 

Take a look at http://github.com/timheuer/strava-net

-th

 

---

From: strav...@googlegroups.com on behalf of Klaasjan M. <mors...@gmail.com>
Sent: Sunday, November 25, 2018 11:59
To: Strava API
Subject: Re: Feedback requested: http://developers.strava.com