Hi @msteam @Durkin — hoping you can help locate or escalate our production API access request.
I’m Ethan O’Neal, founder of PlayersLab, a baseball player-development app live on the iOS App Store. Our WHOOP integration is fully built, deployed, and running against the 10-member development cap. Approval is the only thing between it and our users.
Timeline:
- Submitted the production access request twice
- Most recent submission acknowledged June 26, 2026 (“WHOOP API Request Received”)
- No decision, no denial, and no stated reason in ~60 days
- Our developer dashboard has now reverted to showing “Request Approval” again
I’m posting rather than filing a third Typeform because I’ve read the other approval threads here and it appears requests sometimes can’t be located on your side. I don’t want to keep resubmitting and pushing our own application to the back of the queue.
What we do with the data: PlayersLab computes a daily readiness score for throwing athletes by combining training workload (pitch counts, acute:chronic workload ratio) with recovery signals. WHOOP’s recovery score, HRV, resting heart rate, and sleep are the strongest inputs available for that — they tell a pitcher whether his arm is genuinely ready that day. Scopes requested are read-only: read:recovery, read:sleep, read:cycles, read:workout, read:profile, read:body_measurement. No writes.
Data handling: OAuth 2.0 authorization code flow, per-user explicit opt-in, tokens exchanged and stored server-side (never in the app binary), encrypted in transit and at rest, row-level access control so a member’s data is only readable by that member. Disconnecting purges the stored connection. The connect card already carries the required “Works with WHOOP” attribution. We support Apple Health, Polar, Oura, and Fitbit on the same architecture.
Why it matters now: we’ve signed our first paid college baseball program and are onboarding coaching organizations. WHOOP is the wearable our athletes most commonly already own — every week we’re capped at 10 members is a week we’re either disabling that capability for new users or pointing them toward a competitor’s band. I’d much rather be sending WHOOP members your way.
Could someone either approve the existing request, tell me the specific blocker so I can fix it, or give a realistic review timeline? Happy to share our client ID and the submission confirmation privately, and happy to demo the integration.
I also emailed [email protected] today with the same details.
Thanks —
Ethan