Skip to main content

Version 2026-09-11 (GA)

Lovable-Version: 2026-09-11 This is the first generally available version of the Lovable API.

is_remix on project details

GET /v1/projects/{project_id} and PATCH /v1/projects/{project_id} return is_remix, which is true when the project was created by remixing another project. The response does not identify the source project.

Workspace folders

You can read a workspace’s folders and see which folder each project is in:
  • GET /v1/workspaces/{workspace_id}/folders lists the workspace’s folders with id, name, parent_id, created_at, and updated_at. The list includes a personal folder only when you created it, were given access to it, or are the workspace owner.
  • GET /v1/projects, GET /v1/projects/{project_id}, and GET /v1/workspaces/{workspace_id}/security-center/insights/projects return folder_id, which is null when the project is in no folder.
  • GET /v1/projects and GET /v1/workspaces/{workspace_id}/security-center/insights/projects accept the folder_id and is_in_folder query parameters. The folder_id filter matches projects placed directly in the folder, not projects in its subfolders.
  • The is_in_folder filter selects projects in any folder when true, or projects in no folder when false. You cannot set is_in_folder=false together with folder_id.

Security scan before publishing

When your workspace has Block publishing with critical issues enabled, POST /v1/projects/{project_id}/publish runs the quick security scan on the version you publish before the deployment starts. Unresolved critical findings return 400 with type: security_critical_findings, and props.finding_refs lists the findings.

List project collaborators

GET /v1/projects/{project_id}/collaborators lists the users individually granted access to a project, with their access_level, invited_at, accepted_at, and last_accessed_at. Access through groups, folders, or a workspace role is not listed. Each user_id matches a user_id from GET /v1/workspaces/{workspace_id}/members.

role on workspace member details

GET /v1/workspaces/{workspace_id}/members/{user_id} returns role, with the same values as the workspace members list.

Events & Hooks payloads in the API reference

The API reference documents the requests Lovable sends to your Events & Hooks endpoint:
  • The project.created.v1, project.published.v1, project.workspace_transferred.v1, and project.deleted.v1 events.
  • The message.before_submit.v1 hook, with the allow or deny decision your endpoint returns.

Analytics counts visits without cookies

From October 26, 2026, Lovable analytics no longer uses cookies. The analytics endpoints count a new visit on every page load, including reloads and new tabs. A visitor who moves between pages in an app without reloading stays in one visit. The response fields do not change.
  • visitors is about 20% higher for a typical app. pageviews stays about the same.
  • bounce_rate, session_duration, and pageviews_per_visit are calculated from the new visits. A visit counts as a bounce only when it has one page view and lasts less than 10 seconds.
  • Visits from headless browsers are counted as bot traffic and excluded.
  • Numbers for days before October 26, 2026 do not change, so compare periods on the same side of that date.

email and joined_at in the workspace members list

Each member in GET /v1/workspaces/{workspace_id}/members includes two new fields:
  • email: the member’s email address in this workspace, or null when unavailable.
  • joined_at: when the member joined the workspace, or null when no join time is recorded.

Security insight filters match summary counts

The finding_type_id filter on GET /v1/workspaces/{workspace_id}/security-center/insights/projects uses the same category rules as project_count in GET /v1/workspaces/{workspace_id}/security-center/insights. A project that matches a more specific related finding type is excluded from the broader type, so the filtered list matches the count.

role in the workspace members list

Each member in GET /v1/workspaces/{workspace_id}/members includes role: workspace_owner, workspace_admin, workspace_editor, workspace_viewer, or external_collaborator. Handle unknown values, because Lovable can add roles.The role filter accepts these values and the aliases owner, admin, editor, member, viewer, and collaborator. Both member and editor select workspace_editor.

Find a project in security insights by ID

The query parameter on GET /v1/workspaces/{workspace_id}/security-center/insights/projects matches a full project ID exactly. Other queries search project names and owners.

Make a published app public under a publishing policy

When your workspace has a publishing policy enabled, PATCH /v1/projects/{project_id}/publish cannot set audience to public on a published app that is not public. That request returns 409 with type: publish_visibility_requires_publish. To make the app public, set audience to public on POST /v1/projects/{project_id}/publish. That request also publishes the latest saved version.

Sort workspace members by name

On GET /v1/workspaces/{workspace_id}/members, sort_by=name and its alias sort_by=display_name sort case-insensitively by the returned name. Members without a name sort first in ascending order and last in descending order. Cursors issued under the earlier name ordering are rejected, so restart pagination from the first page.

Access requirements in error responses

When a plan, feature, permission, or scope check fails, the error’s props names what the request needs:
  • required_plan on payment_required: the minimum plan, pro, business, or enterprise.
  • required_features on payment_required: the feature permissions a feature check requires.
  • required_permissions on forbidden: alternative permission sets. All permissions in any one set satisfy the check.
  • required_scopes on insufficient_scope: the credential scopes that satisfy the check. Any one of them is enough.
The props object describes the check that failed. Other checks can still reject the request.

Workspace member names and details

You can read member names and look up a single member:
  • GET /v1/workspaces/{workspace_id}/members returns each member’s name, or null when unavailable, and accepts sort_by=name.
  • GET /v1/workspaces/{workspace_id}/members/{user_id} returns one active member’s name and email. Pass a user_id from the members list.

Grouped findings in security insight counts

On GET /v1/workspaces/{workspace_id}/security-center/insights/projects, the error_count, warning_count, and info_count values in review_priority_explanation count a group of related findings once, at the level of its most severe finding. The counts match the issues the project’s Security view lists.