App approval (10-user limit) - submitted Jun 22 and again Jul 29, no response in 64 days (Soluno)

Hello WHOOP team,

We submitted an App Approval request (user limit increase) on June 22, 2026 through the official form, and submitted it again cleanly on July 29, 2026. Both times we received only the automated “WHOOP API Request Received” email. 64 days later there has been no response from a person - no questions, no rejection, no timeline.

App: Soluno - a Russian-language companion for WHOOP members.
Client ID: 2697535c-4244-4855-ae3c-b4331835b30e

Why the app exists: the official WHOOP app is English-only in our region. Members here own the device and pay for the membership, but many cannot read their own recovery, strain and sleep insights well enough to act on them. We read their data through the official API v2 (OAuth, read scopes only) and present it in Russian in plain language. Without an active WHOOP membership and device our app does nothing - we are a complement to WHOOP and never present ourselves as an alternative.

Everything on your approval checklist is complete:

  • API Terms of Use accepted.
  • Tested with real WHOOP members within the 10-member development cap.
  • App Name, Contact Email and Privacy Policy URL filled in the dashboard and accurate. The privacy policy is live and publicly reachable: Privacy Policy — Soluno
  • Design and Brand Guidelines followed: your metric names kept in English next to the Russian translation, mandated score colors unchanged, “Data by WHOOP” attribution shown in the UI, WHOOP named only as a compatibility statement, and a visual design that is entirely our own.
  • Official API only - no scraping, no reverse engineering, no unofficial endpoints.
  • No medical claims.

Expected load: 200-500 members, roughly 3,000-7,500 API calls per day - inside the existing 10,000/day application limit. We are not asking for a rate limit increase, only for the member cap.

We also opened a written request on July 1 that became Membership Services case 07476326. Support replied on July 7 only to redirect us to developers@whoop.com; we have written there as well and submitted a request through the Developer Dashboard support form.

We are ready to send a build, screenshots, a demo account, or to walk someone through the app on a call. All we are asking for is confirmation that the submission is in the queue and a rough timeline. @msteam @Durkin

Thank you.

Update, and a finding that probably affects everyone in this thread.

WHOOP Support told me on July 7, 2026 to send developer inquiries to developers@whoop.com. I did, on August 24. It bounced immediately:

550 5.1.1 The email account that you tried to reach does not exist.
Final-Recipient: rfc/822; developers@whoop.com

So the address WHOOP Support hands out for developer questions is dead. If you were told the same thing and never heard back, your message may simply never have arrived. The developer docs page on support (developer.whoop.com/docs/developing/support/) lists no developer email at all - only the support form in the Developer Dashboard.

Status on my side is unchanged: App Approval submitted June 22 and again July 29, 2026 (Client ID 2697535c-4244-4855-ae3c-b4331835b30e), automated acknowledgements both times, 67 days, no human response. Dashboard support form submitted August 24, no reply yet.

@msteam @Durkin - could someone fix the developers@whoop.com routing and confirm the approval queue is being worked?

Same issue here - and it seems to affect the Affiliate program as well.

WHOOP Support specifically told me to contact affiliates@whoop.com regarding the status of my affiliate application. I emailed that address, but the message bounced immediately with:

5.2.1 The email account that you tried to reach is inactive.

I sent the bounce screenshot back to WHOOP Support. One agent then told me there is actually no way to contact the Affiliate team after submitting an application and that applicants just have to wait. Another agent later asked me to send a screenshot of the bounce error again, even though I had already provided it earlier in the same support thread.

Also, we are seeing a very similar problem with WHOOP API access requests. We have been waiting for a response for more than six months and have submitted the API access application multiple times, but still have not received any meaningful update.