KBAISE/ for lovable
Library
Docs

Integration security

about 10 minShippingchecked 5d agoOfficial page
The short version

Lovable connects to third-party tools through a secure gateway so your secret keys never leak into your app code. Your app only has access to what your connected account can see, and all traffic comes from fixed web addresses you can safely allow.

Anyone connecting third-party services to their app who needs to configure firewalls, lock down API keys, or ensure data stays secure.

Do this, in order

  1. 1

    Check the permission level of the account you use when connecting an integration.

    Your app can only see and edit what that specific user account is permitted to access in the third-party service.

  2. 2

    Add Lovable's IP ranges (IPv4: 185.41.150.0/25 and IPv6: 2a07:8241:fca::/48) to your firewall or external service allowlist.

    This permits your external service to accept secure incoming requests sent through Lovable's gateway.

  3. 3

    Set domain restrictions on any public frontend API keys using *.lovable.app/*, *.lovable.dev/*, *.lovableproject.com/*, and your custom domain.

    This stops attackers from copying your public browser keys and using them on unauthorized websites.

  4. 4

    Manually delete integrations in your workspace settings as soon as you stop using them.

    Unused connections are never deleted automatically, but deleting one immediately wipes its secrets and cuts off access.

  5. 5

    Rotate your project's Lovable API key if you ever suspect a credential has been leaked.

    Rotating the key invalidates compromised project credentials within an hour.

Paste this into your project

Review all external API integrations and connectors in this project to ensure no private secrets or API keys are exposed in client-side code. Confirm that requests use backend connector routes or public keys intended for browser use.

Words decoded

connector gateway
A secure middleman server run by Lovable that talks to outside services on your app's behalf without exposing secret keys.
IP allowlisting
Telling a service to only accept requests coming from specific, pre-approved digital addresses.
domain restrictions
Rules that limit where a public key can be used so it only works on your specific website addresses.

Where people get stuck

  • Old or expired connections are never cleaned up automatically; you must delete them manually to remove their stored credentials.
  • Gateway connectors have a default rate limit of 1,000 requests per minute per project, which high-frequency automations might hit.
  • Rotating an API key takes up to an hour to fully invalidate the old cached key.
  • Custom MCP servers do not route through the standard connector gateway by default unless you are on an enterprise plan with static IPs enabled.

The short version, steps, decoder and prompt on this page are written automatically from Lovable's own documentation and can lag or misread it. The official page is always the authority.