How to Integrate Lovable with Postman

In Lovable, click the Cloud tab (the '+' icon next to the preview panel) to open the project settings. In the Cloud tab, navigate to the project overview where you can find your Supabase project reference ID — it is the alphanumeric string in your project URL. Your Edge Function base URL follows the pattern https://{project-ref}.supabase.co/functions/v1/{function-name}. For the Supabase anon key, look in Cloud → Project Settings or in your Lovable project's source code under src/integrations/supabase/client.ts where it appears as the SUPABASE_PUBLISHABLE_KEY environment variable. The anon key always starts with 'eyJ' (it is a JWT token). You will need this key as an authorization header when calling Edge Functions that require authentication. For Edge Functions without authentication — those that do not call supabase.auth.getUser() or check for an Authorization header — you can call them without any headers in Postman. Write down or copy both the base URL and the anon key before proceeding to Postman.

Open Postman (web or desktop app) and click 'Collections' in the left sidebar, then click the '+' button to create a new collection. Name it something like 'MyApp Edge Functions'. Within the collection, you can organize requests into folders by feature area — for example, a 'Payments' folder for Stripe-related Edge Functions and a 'Users' folder for user management functions. Next, create Postman environments for development and production. Click 'Environments' in the left sidebar and click '+' to create a new environment named 'Lovable Development'. Add two variables: SUPABASE_URL with the value of your Supabase project URL (e.g., https://abcdefgh.supabase.co) and SUPABASE_ANON_KEY with your anon key value. Create a second environment named 'Lovable Production' with the same variable names but pointing to your production Supabase project if you have one. Using environments means your request URLs use {{SUPABASE_URL}} as a placeholder — when you switch the active environment in Postman's top-right dropdown, all requests automatically point to the correct project. This pattern prevents the common mistake of accidentally running test requests against production data.

Inside your Postman collection, click the three dots next to the collection name and select 'Add request'. Name the request after your Edge Function (e.g., 'GET weather-proxy' or 'POST stripe-webhook'). In the request URL field, type {{SUPABASE_URL}}/functions/v1/{your-function-name} using the environment variable placeholder. For the method, select GET or POST as appropriate for your function. Under the Headers tab, add two headers: Authorization with value Bearer {{SUPABASE_ANON_KEY}} and Content-Type with value application/json. The Authorization header is required for Edge Functions that use Supabase Auth — the anon key tells the function which Supabase project it belongs to. For POST requests, click the Body tab, select 'raw', and choose JSON from the dropdown. Enter a sample JSON payload that your function expects. Click the Save button to save the request to your collection. Add one request per Edge Function, naming them clearly. For each request, you can add a description in the 'Documentation' tab explaining what the function does, what parameters it expects, and what response structure to expect — this becomes your team's API reference.

With your Postman environment set to 'Lovable Development' (select it from the top-right dropdown), click 'Send' on your first request. The response panel at the bottom shows the HTTP status code, response time, response body, and headers. A 200 response with the expected JSON payload confirms the Edge Function is working correctly. For a 401 Unauthorized response, verify the Authorization header is present and the anon key is correct. For a 500 error, check the response body for the error message your Edge Function returns — then open Cloud → Logs in Lovable to see the full stack trace from Deno. For a CORS error (which appears in Postman as a connection refused or missing response headers), note that Postman itself does not enforce CORS — CORS errors only occur when calling from a browser. If you are getting a CORS error in your browser-side frontend but not in Postman, the issue is specifically in the CORS headers your Edge Function returns. Postman's response time display is also useful for identifying slow Edge Functions — anything over 2,000ms warrants investigating the function's logic or the upstream API it calls. For complex cases, RapidDev's team can help set up automated Postman test suites with pre-request scripts and test assertions for your Lovable Edge Functions.

Once your collection is tested and documented, Postman provides two ways to share it with your team. For sharing a live collection that updates when you modify requests, click the three dots next to your collection name, select 'Share', and copy the collection link — anyone with this link can view and fork the collection in Postman. For exporting a static snapshot, click 'Export' and choose Collection v2.1 JSON format — this creates a .json file you can commit to your GitHub repository alongside your code. This is particularly useful for open-source projects or for teams that want their API documentation version-controlled. For a publicly browsable web documentation page, click the three dots on your collection and select 'Publish Docs' — Postman generates a formatted HTML page at a public URL that shows all requests, parameters, and example responses. This page is readable by non-developers, making it useful for showing stakeholders or clients what your Lovable app's backend can do. Update the collection whenever you add or modify Edge Functions in Lovable to keep the documentation current.