Polar authentication

Polar authentication lets your users sign in with their Polar account. Once connected, you can offer “Continue with Polar” in your WeWeb app.

What this integration supports

• Social sign in with Polar
• Redirect to different pages for success, error, and first-time users

Setup in Polar

You create an OAuth 2.0 client in Polar and register WeWeb’s redirect URL (the URL Polar sends users back to after sign in).

1. Create an OAuth client

1. Open your Polar settings: Polar OAuth settings.
2. Click Create OAuth Client.
3. Fill in the required fields:
   • Application Name
   • Client Type
   • Redirect URIs
   • Scopes
   • Homepage URL
4. Add this redirect URI:
   • https://<your-domain>/api/auth/callback/polar

Polar blocks http:// redirect URIs (except for localhost). If you are testing locally, use http://localhost/... only where Polar allows it.

5. Create the client and copy:
   • Client ID
   • Client Secret

2. Add additional redirect URIs (optional)

If you use multiple environments, add one redirect URI per environment (preview, staging, production).

Connect Polar in WeWeb

1. In the WeWeb editor, go to Data & API → Auth → Integrating providers.
2. Find Polar and expand it.
3. Turn on the Enable toggle.
4. Paste:
   • Client ID
   • Client Secret
5. Click Save.

WeWeb stores these values as environment variables (for example PROVIDER_POLAR_CLIENT_ID and PROVIDER_POLAR_CLIENT_SECRET).

Test sign in

1. In Interface, add a “Continue with Polar” button.
2. Create a workflow on click and add Sign in with social provider.
3. Set:
   • Provider: polar
   • Success page, Error page, And (optional) New user page
4. Preview your project and complete the Polar sign-in flow.

For what to do after sign in (roles, private pages, and access checks), see Users and roles overview →.

Common pitfalls

Redirect URI must use https

Polar blocks http:// redirect URIs (except for localhost).

• Use https:///api/auth/callback/polar for staging and production.
• If you test locally, use http://localhost/... only if Polar allows it for your setup.

Redirect URI mismatch

If Polar shows a redirect URI error, the registered URI does not match the one your app is using.

• In Polar, confirm the exact redirect URI is registered (including https:// and the full path).
• Make sure you are testing on the same domain you registered (preview vs production).

Reference

WeWeb settings

Setting in WeWeb	Description	Where to find it in Polar
Client ID	Identifies your Polar OAuth client.	Polar OAuth settings (Client ID).
Client Secret	Secret used to securely complete sign in.	Polar OAuth settings (Client Secret).

FAQs

Which redirect URI should I add in Polar?

Add https://<your-domain>/api/auth/callback/polar. Add one redirect URI per environment you use.

What provider value should I use in the workflow action?

Use polar as the Provider value in the Sign in with social provider action.

Continue learning

Next, learn how to control access after users sign in.

Users and roles overview →