Lovable API

1. 1

   Understand what you want to achieve with the API, such as deploying a project, checking security, or embedding a project.

   The Lovable API can do many things, so knowing your goal helps you find the right part of the API.

2. 2

   Create an API key in your Lovable workspace settings.

   You need an API key to prove you are authorized to use the API and access your projects and workspace.

3. 3

   If you use Postman, fork the Lovable API collection into your Postman workspace and set up your API key in a Postman environment.

   This provides pre-built examples for every API function, making it easier to test and understand how to use the API.

4. 4

   Use your API key in your own scripts or services to make calls to the Lovable API.

   This allows your external tools to interact with Lovable, automating tasks like publishing projects or reading analytics.

I need to automate deploying my Lovable projects and monitor my workspace. Can you help me set up the Lovable API for this? I'm on a Business plan.

REST API

A standard way for different computer programs to talk to each other over the internet, like sending requests and receiving responses.

Programmatically

Doing something automatically using computer code or scripts, rather than manually clicking buttons on a website.

Workspace

Your personal or team area within Lovable where all your projects and settings are stored.

Embed

To place a Lovable project's preview directly into another website or application, so it appears as part of that other product.

PII labels

Labels that identify 'Personally Identifiable Information' within your projects, like names or addresses, which helps with data privacy.

Endpoint

A specific address within the API that performs a particular action or provides specific information, like 'get project details'.

Postman

A popular tool that helps people test and build with APIs by making it easy to send requests and see responses.

• Trying to use the API without a Business or Enterprise plan, as API key creation requires one.
• Attempting to read PII labels or use per-project security inventory without an Enterprise plan and 'Sensitive data scanning' enabled.
• Confusing the Lovable API with the Lovable MCP server or API connector; they serve different purposes and run in different places.
• Expecting the API to create or edit AI projects directly; the API manages existing projects, while AI project creation/editing is via the MCP server.
• Not understanding that embedding a project via the API generates a temporary preview URL, not the full editor or published app, and doesn't require a Lovable login for visitors.