Third-Party API Integration Not Working in Base44
You've configured a third-party API integration in your Base44 app (such as connecting to Stripe, SendGrid, Airtable, or a custom REST API), but the integration fails. Requests return errors, data doesn't sync, or the connection times out.
API integrations are critical for extending Base44 apps with external services. A broken integration can prevent payment processing, email sending, data synchronization, or any other external functionality your app depends on.
The issue may manifest differently: some API calls succeed while others fail, or the integration works from the editor but fails in the published app.
Error Messages You Might See
Common Causes
- API keys or authentication tokens are incorrect, expired, or not set in the production environment
- CORS (Cross-Origin Resource Sharing) policies block client-side API calls from the published app's domain
- The request format (headers, body, content type) doesn't match what the third-party API expects
- The API endpoint URL is wrong or the API version has been deprecated
- Rate limits on the third-party API are being exceeded
How to Fix It
First, verify the API credentials are correct and set in the production environment. Test the API call directly using a tool like Postman or curl to confirm the credentials and endpoint work outside of Base44.
If the call works in Postman but not in Base44, the issue is likely CORS. Client-side API calls from a browser are subject to CORS restrictions. The call may need to be routed through a server-side function.
For integrations with complex authentication (OAuth, signed requests) or APIs that require specific header configurations, a developer can set up the integration to work reliably in the production environment.
Real developers can help you.
You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.
Get HelpFrequently Asked Questions
Why does my API integration work in Base44 preview but not when published?
The most common cause is CORS restrictions or missing environment variables in production. Client-side API calls from a different domain may be blocked by the API's CORS policy.
How do I fix CORS errors in Base44?
CORS blocks browser-to-API calls from different domains. Route your API calls through a server-side function instead of making them directly from the client-side. A developer can help set this up.