Skip to main content
Question

How to register a second app with the Strava API as the same developer?

  • May 16, 2026
  • 2 replies
  • 205 views
Forum|alt.badge.img

Hi everyone,

I'm a developer currently running two separate fitness applications — Pacewar (pacewar.com) and Swimstro (swimstro.com) — and I'd like to integrate both with the Strava API.

I've already registered Pacewar through my existing Strava account and the integration is live. Now I'd like to register Swimstro as well, but the API settings page doesn't seem to allow more than one app per account.

My questions are:
1. Is it possible to register multiple apps under the same Strava developer account? If so, how?
2. If not, is the recommended approach to create a separate Strava account for each application?
3. Are there any policy concerns I should be aware of when running two distinct Strava-integrated apps as the same developer?

Both apps are independent products targeting different audiences — Pacewar focuses on running, while Swimstro is built for swimmers — so they are genuinely separate integrations.

Any guidance from the community or the Strava team would be greatly appreciated!

Thanks,
Fabio
Developer – Pacewar & Swimstro

2 replies

Jan_Mantau
Forum|alt.badge.img+26
  • Jan_Mantau
  • Hub Powerhouse
  • May 17, 2026

if it’s not feasible for you to connect only one app to Strava as an entry gate for the two actual apps you will need the second Strava account.

    Forum|alt.badge.img
    • Brian B.
    • Hub Starter
    • August 25, 2026

    Like Fabio I am a developer with 2 distinct apps that required separate accounts. Both are iOS native mobile apps each with a different purpose and user groups. My first published app was created using my personal subscriber account I have had for years. I use it for personal fitness tracking and it will not go away anytime soon.

    For my second app, like other developers in this situation, I created a second (what I call a “burner”) account only for hosting an app - it will never be used to track activities or follow other athletes. It’s perflexing to me why Strava decided to do it this way. It ends up creating a whole bunch of burner accounts when a more intuitive developer platfom would allow single developers up to large development organizations manage a suite of apps under one account. The dev account could even be distinct, and separate, from an end user/athlete account. Charge the account on a base subscription plan plus usage.

    A problem compounded. 2 apps - 2 accounts. Now we have paid API access gated by an app owner requirement to be a subscriber. This works for my first app but now I have this burner account that also requires a subscription. It doesn’t sit right. Now I have decisions to make once the 3 month free trial expires on second account. I may end up retiring an app or dropping Strava integration because the cost is not sustainable for me which is really a shame when this could have been possible with a properly implemented developer program.

    -Brian.

    Terms & ConditionsAccessibility statement