List security scan findings
Changed onPlan: Business or higher
Scope: projects:read
Returns a page of findings in the scan snapshot, including results reused from earlier scans and findings marked fixed or ignored. Findings are ordered by scanner_name, ascending, with a stable order within each scanner. Follow pagination.next_cursor until pagination.has_more is false to retrieve the complete snapshot.
Request
- Base URLhttps://api.lovable.dev
- Auth
- API key in header Lovable-API-Key
- or HTTP bearer
Path parameters
Project ID.
Security scan ID returned by the list endpoint.
Query parameters
Maximum number of items to return per page.
Pass pagination.next_cursor from the previous response to fetch the next page. Omit for the first page; keep the same filters and sort order across pages.
Headers
Stable API version to serve, as a YYYY-MM-DD date. Omit for the oldest supported stable version, currently 2026-09-11.
Comma-separated beta revision strings to enable on top of the stable version.
Response
OK
Example response
{
"data": [
{
"category": "data_exposure",
"created_at": "2026-01-15T09:30:00Z",
"description": "A public table has row-level security disabled, exposing all rows to anonymous clients.",
"id": "b2c3d4e5-f6a7-8901-bcde-f23456789012",
"level": "error",
"name": "Row-level security disabled on a public table",
"scanner_name": "agent_security",
"status": "open",
"updated_at": "2026-01-15T09:30:00Z"
}
],
"pagination": {
"has_more": true,
"next_cursor": "eyJ2IjoxLCJpZCI6InByal8wMWp3M2s5In0"
}
}Changes
- warning
added the new
suppressedenum value to the//response property for the response status - info
for the
headerrequest parameterLovable-Version, the format was generalized fromdateto no format - info
added the non-success response with the status
- warning
- info
added the non-success response with the status
- info