Skip to main content
Answered

New strava policy and dev, test, prod accounts

  • June 11, 2026
  • 3 replies
  • 22 views
P
Forum|alt.badge.img+1

Good morning,

I'm wondering what best practice could be given regarding the usage of different Strava accounts for different environments. While searching the internet I read that Stava expects to have only one application using a client ID. Which would imply a different client ID per application, but also for the different environment in use.
Currently I do local development, but I run a test and production server. So I use three client id's. Which becomes expensive if I need to pay for each of them. Or can it be bundled into one developer having a subscription?

Thanks for your thoughts and answers.

Pieterbas

Best answer by Mark_AJ

Hi ​@Pieterbas is your app in production live with more than 10 users? If not, I’m not sure why you need separate client IDs if they’re for the same application. Even if it is more than 10 users, if it is the same application, I still don’t see a reason to separate client IDs for each environment. Separation of concern can easily be done via deployment and database separation.

3 replies

M
Forum|alt.badge.img+3
  • Mark_AJ
  • Hub Rookie
  • Answer
  • June 11, 2026

Hi ​@Pieterbas is your app in production live with more than 10 users? If not, I’m not sure why you need separate client IDs if they’re for the same application. Even if it is more than 10 users, if it is the same application, I still don’t see a reason to separate client IDs for each environment. Separation of concern can easily be done via deployment and database separation.

P
Forum|alt.badge.img+1
  • Pieterbas
  • Author
  • Hub Rookie
  • June 11, 2026

Dear ​@Mark_AJ ,

Thank you for your reply!!

I’m not yet accepting any registrations yet, so no I’m only testing with a few people still below the limit of ten people.

On my side I’ve duplicated the infra for test and production. So I can do most of the testing on my server. However the callback domain is limited to one url. So that should be connecting to the production environment. But how can I have people connect to test with only one callback domain. Also I was thinking that the webhook registration would only allow for one per client id. So testing the interaction between the Strava API and my software is not possible without impacting the user community.

do I make mistakes in my assumptions and reasoning?

 

kind regards, pieterbas

C
Forum|alt.badge.img+9
  • Cyril
  • Hub Explorer
  • June 11, 2026

Hi ​@Pieterbas, you could use a single client ID and simply have your production environment relay the webhooks to your dev/test environment(s). 

On a related note, there’s currently no way to authenticate the Strava webhooks, so I’d suggest having your prod use an IP whitelist for incoming webhooks (see https://communityhub.strava.com/developers-api-7/whitelist-ip-address-webhook-1840?postid=20447#post20447), and your dev/test whitelisting your prod IP.

Terms & ConditionsAccessibility statement