Why does WHOOP auth fail with unknown_error after the user approves?

The usual cause is a Client ID or Secret saved in Terra that doesn't match your WHOOP app, so WHOOP rejects the token exchange.

The usual cause is a Client ID or Secret saved in Terra that doesn't match your WHOOP app. After the user approves, Terra exchanges the authorisation code with WHOOP using the credentials saved on your WHOOP connection. If WHOOP rejects them, the user is sent to your failure redirect with unknown_error.

Causes seen in practice include a secret pasted one character short and a URL pasted into the secret field. Neither is easy to spot by eye.

1

In the WHOOP Developer Dashboard, open your app and copy the Client ID and Client Secret.

2

In the Terra dashboard, open Connections > Sources > WHOOP on the environment your users connect through, and paste both values in full, with no leading or trailing spaces.

3

Save, and make sure the save completes. Credentials are saved per environment, so repeat this on each environment you use.

4

Run a new connection. Users whose connection failed need to start the flow again.

If the redirect URL is the problem instead, WHOOP stops the flow at its own authorisation step, because the redirect URL in the request must match the one registered on your WHOOP app. See How do I set up WHOOP provider credentials?