OAuth Apps: Secure Tokens for Connecting to Paminga
OAuth Apps let you generate OAuth 2.0 tokens to securely connect external systems to your Paminga instance.
If you're plugging Paminga into a custom integration, an ecommerce platform, or your own backend, OAuth Apps is where you start. OAuth 2.0 is the industry-standard protocol for authorization — and using it here means you're not passing static API keys around your codebase.
What You Can Do With an OAuth App
Generate a token from an OAuth App and you can:
- Trigger Abandoned Cart Automations from your ecommerce backend
- Trigger Product Recommendation Automations from your shop or app
- Make authenticated calls to Paminga's GraphQL API for anything else
Three doors, one key model.
Creating an OAuth App
The setup is intentionally short:
- Open Account Settings → OAuth Apps
- Click Create OAuth App
- Add a description and save
You'll get a client_id and a secret. Use them via the standard OAuth 2.0 flow to generate tokens.
Why OAuth, Not Just API Keys
OAuth is the standard for a reason. Tokens are short-lived. Refresh flows are explicit. Revocation is real. If a token gets compromised, you revoke the app — not your entire integration footprint.
❌ Don't hardcode a long-lived API key into a shell script and copy it into a Slack DM.
✅ Do create a named OAuth App for each integration that needs Paminga access. When you decommission the integration, revoke its app.
A Few Practical Notes
- Create one OAuth App per integration. Don't share a single app across multiple systems. If you have to revoke, you'd take everyone down.
- The description is for your future self. "Production Shopify webhook handler" beats "test".
- Permissions on creating OAuth Apps live in Permissions. Most teams should restrict this to platform admins.
Get Started
- Open Account Settings → OAuth Apps
- Click Create OAuth App, name it after the integration
- Use the
client_idandsecretin the standard OAuth 2.0 flow - Call Paminga's API or trigger Abandoned Cart / Product Recommendation Automations with the resulting token
Read the OAuth Apps docs and the API docs to dig in.



