Common Issues
general
Third-Party Integration Not Working (APIs, Webhooks, OAuth)
Your app integrates with a third-party service (Google, Stripe, Twilio, OpenAI, etc.) and the integration stopped working or never worked properly. API calls fail, webhooks don't fire, or OAuth login redirects go nowhere.
Common Causes
- API keys expired, revoked, or not set in production
- Webhook URL points to localhost or an old deployment URL
- OAuth redirect URIs don't match the actual app URL
- Rate limits hit — the API is blocking requests because you're making too many
- API version changed and the integration code uses an outdated version
How to Fix It
- Check the third-party service's dashboard for error logs or failed requests
- Verify all API keys are current and set in your production environment
- Update webhook URLs to point to your production domain
- Check OAuth redirect URIs in the third-party service's settings
- Test the API calls directly (using Postman or curl) to isolate the issue
Real developers can help you.
Describe what's wrong in plain English. No technical knowledge needed.
Get HelpFrequently Asked Questions
The integration worked before. Why did it stop?
API keys might have expired, the service might have updated their API version, or your webhook URL might have changed after a redeployment.
Can a developer set up the integration properly?
Yes. A developer can debug the failing integration, update API configurations, and ensure everything is properly connected.