Got tired of explaining OAuth setups to clients, so we created a directory of step-by-step tutorials for getting API keys from 200+ popular tools.
Check out r/getCredentials for the community.
The Problem Every Developer Recognizes
You know this scenario: You're integrating with a client's Salesforce, need their API credentials, and suddenly you're scheduling a screen share to walk them through their admin panel. Again.
Or you're building a Microsoft 365 integration and spending 30 minutes explaining why they need a "client secret" instead of just their password.
These aren't technical problems - they're communication problems. And they eat up way too much development time.
What We Actually Built
We started collecting step-by-step tutorials for the most common credential requests we kept having to explain.
What began as internal documentation turned into a directory of 200+ tutorials covering:
Microsoft 365 (Exchange, Teams, SharePoint, etc.)
Google Workspace (Gmail, Drive, Calendar, etc.)
Salesforce (various API types and permission levels)
HubSpot, Slack, Notion, Airtable - you name it
Each tutorial is visual, platform-specific, and written for non-technical users. Instead of explaining OAuth flows, you send a link.
How It Works in Practice
Instead of writing "Please generate an API key for your Salesforce org" and dealing with the inevitable confusion, you send a tutorial that shows:
Exactly which Salesforce menu to click
Screenshots of each step
What each field means and what to enter
How to copy the credentials correctly
Your client follows the steps, gets the credentials, and sends them back. No calls, no back-and-forth emails, no project delays.
The Developer Community Part
We started r/getCredentials because we realized other developers were solving the same problems. The subreddit has become a place to:
Share which platforms are causing the most client confusion
Request tutorials for new integrations
Discuss credential collection best practices
The directory covers most of the tools developers commonly integrate with:
CRM platforms (Salesforce, HubSpot, Pipedrive, etc.)
Email/Calendar (Microsoft 365, Google Workspace, Outlook)
Project management (Asana, Monday, Notion, Airtable)
Communication (Slack, Teams, Discord)
E-commerce (Shopify, WooCommerce, BigCommerce)
Social media (Facebook, LinkedIn, Twitter APIs)
Plus a bunch of niche B2B tools that always seem to have the most confusing credential setup processes.
The Honest Assessment
This isn't revolutionary - it's just documentation done properly. But it solves a real problem: client credential collection shouldn't take days or require phone calls or a meeting.
If you're dealing with this regularly, the directory might save you some time. If you're not, you probably don't need it.
What's the most confusing credential setup you've had to explain to a client? Drop it in r/getCredentials - we might already have a tutorial for it.