Auth
Auth configs, auth modes, and managed vs custom.
An auth config is your side of a connection — the OAuth app or API integration you own, stored encrypted per project. It's the template an end-user's connected account authorizes against.
Auth modes
Providers declare which modes they support. Each specifies the credential fields a user provides and the scopes it unlocks:
| Mode | The user provides | Used by |
|---|---|---|
oauth2 | An authorization (redirect + consent) | Zoho Books, Google, Slack, Shopify |
api_key | An API key / secret | Sandbox, Razorpay, WhatsApp Business |
webhook_secret | A signing secret for inbound events | Razorpay, WhatsApp Business |
Managed vs custom auth
You can use a Stacklink-managed OAuth app or bring your own auth config. Pick per provider:
| Stacklink-managed | Your own auth config | |
|---|---|---|
| Setup | None — works out of the box | Register an OAuth app, add client id/secret |
| Branding | Users see "Stacklink" on consent | Users see your app's name |
| Scopes | Sensible defaults | Custom scopes |
| Rate limits | Shared across Stacklink | Your app's own quota |
| Best for | Dev & iteration | Production |
Start on managed to ship fast; move to your own auth config before production so users see your brand and you get dedicated scopes and rate limits.
Skip the OAuth-app paperwork to start
Stacklink-managed auth works out of the box on the free plan — connect a provider account today and bring your own OAuth app when you're ready for production.