KBAISE/ for lovable
Library
Docs

List security scans

about 10 minShippingchecked 7d agoOfficial page
The short version

View a project's historical security scans sorted newest first using the Lovable API. This requires a Business plan or higher and returns scan summaries, not individual vulnerability findings.

Teams on a Business plan or higher who want to programmatically track and display security audit history for their project.

Do this, in order

  1. 1

    Create an API key with the projects:read scope in your workspace settings at lovable.dev/settings/api-keys.

    The security scans endpoint requires an API key with permission to read project data.

  2. 2

    Send a GET request to https://api.lovable.dev/v1/projects/{project_id}/security-scans including your API key in the Lovable-API-Key or Authorization header.

    This retrieves the project's list of security scans ordered by start time.

  3. 3

    Use pagination.next_cursor from the response as the cursor query parameter to fetch the next page of scans if pagination.has_more is true.

    Scans are paginated in batches up to 100 items per request.

Paste this into your project

Create a dashboard section that fetches and displays recent security scans for the current project using the Lovable API endpoint GET /v1/projects/{project_id}/security-scans. Show scan start time, status, and scan ID in a table, and include pagination controls that use the cursor parameter to navigate pages.

Words decoded

Scope
A specific permission assigned to an API key that restricts what actions it can perform.
Cursor
A unique marker returned by an API that points to where the next page of results begins.

Where people get stuck

  • Calling this endpoint does not return vulnerability findings directly; you must take the scan_id and call the dedicated findings endpoint.
  • Accounts below the Business plan will receive a 402 payment_required error.
  • API keys are workspace-specific; querying a project from a different workspace returns a 404 not found error.

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.