I am a data engineer and we have 10 WHOOP bands, 6 have been registered. However, the account we used to log in to the Developer Portal and create the app is a user and we need to switch the account to one of our data engineers or have a few of us have login’s. Does anyone have experience with this? This is the developer portal that I am referring to WHOOP Developer Portal.
FYI, I am not Rich (the account I have needed to use to post in the community), I am Hannah, a data engineer.
Thanks in advance for any advice. I have tried emailing support@whoop.com and got the following back… but I don’t even have a settings page! I have a Team page and I have tried to add myself as a member, but that doesn’t work, I still have a pending invite because I get an error when I click the link in the invite email.
-
Changing the primary (owner) account
• Sign in with the current owner account.
• Open Settings ➜ Team (or Organization Settings ➜ Members, depending on your view).
• Click “Invite Member,” enter the new primary user’s email address, and select the Owner role.
• Once that person accepts the invite, you can downgrade or remove the original owner if you wish.
This effectively transfers administrative control—API keys, apps, usage analytics, and billing remain intact. -
How Teams work in the Portal
• Each person you invite appears in the same “Team” space, which lets them:
– Generate or view the project’s API keys/secrets with their own credentials.
– Create new apps or edit existing ones (depending on the role you assign).
– See usage statistics and error logs without sharing a single login.
• Roles can be set to Owner (full admin), Developer (can manage apps/keys), or Viewer (read-only metrics).
• Using separate log-ins keeps audit trails clear and helps rotate access quickly if someone leaves the organisation. -
“Developers should have a WHOOP band”
• Owning a band isn’t a strict requirement to build with the API.
• It is strongly recommended because it gives each developer a real WHOOP member token to test against—especially helpful when validating endpoints that return sleep, strain, or recovery samples.
• If a developer doesn’t have a band, you can still create service-level tokens for server-to-server integrations, but some interactive examples in the docs assume you have member-level data available.