--- title: "Changes to List security scans" method: GET path: "/v1/projects/{project_id}/security-scans" --- # Changes to List security scans `GET /v1/projects/{project_id}/security-scans` > Every recorded change to this operation, newest first. ## Timeline Changed in 7 of 30 revisions. - **2026-09-18** `a83f0776a896`: 2 info - **2026-09-17** `63e95b862209`: 1 info - **2026-09-16** `1eba97261efb`: 1 breaking, 1 info - **2026-09-15** `82dda6df74b8`: 30 breaking, 37 info - **2026-09-14** `8539cafd5cb6`: 2 breaking, 3 info - **2026-09-11** `b19e0179b77a`: 1 info - **2026-09-11** `c7f67a5564ac`: 1 breaking, 15 warning, 2 info ## Changes - **2026-09-18** `a83f0776a896`: 2 info - for the `header` request parameter `Lovable-Version`, the format was generalized from `date` to no format - added the non-success response with the status `503` - **2026-09-17** `63e95b862209`: 1 info - added the non-success response with the status `404` - **2026-09-16** `1eba97261efb`: 1 breaking, 1 info - removed the required property `data/items/scan_id` from the response with the `200` status - added the required property `data/items/id` to the response with the `200` status - **2026-09-15** `82dda6df74b8`: 30 breaking, 37 info - the response property `data/items/commit_sha` became nullable for the status `200` - the response property `data/items/finished_at` became nullable for the status `200` - the response property `detail` became nullable for the status `400` - the response property `detail` became nullable for the status `401` - the response property `detail` became nullable for the status `402` - the response property `detail` became nullable for the status `403` - the response property `detail` became nullable for the status `406` - the response property `detail` became nullable for the status `429` - the response property `detail` became nullable for the status `default` - the response property `errors` became nullable for the status `400` - the response property `errors` became nullable for the status `401` - the response property `errors` became nullable for the status `402` - the response property `errors` became nullable for the status `403` - the response property `errors` became nullable for the status `406` - the response property `errors` became nullable for the status `429` - the response property `errors` became nullable for the status `default` - the response property `errors/items/location` became nullable for the status `400` - the response property `errors/items/location` became nullable for the status `401` - the response property `errors/items/location` became nullable for the status `402` - the response property `errors/items/location` became nullable for the status `403` - the response property `errors/items/location` became nullable for the status `406` - the response property `errors/items/location` became nullable for the status `429` - the response property `errors/items/location` became nullable for the status `default` - the response property `props` became nullable for the status `400` - the response property `props` became nullable for the status `401` - the response property `props` became nullable for the status `402` - the response property `props` became nullable for the status `403` - the response property `props` became nullable for the status `406` - the response property `props` became nullable for the status `429` - the response property `props` became nullable for the status `default` - the response property `data/items/commit_sha` became required for the status `200` - the response property `data/items/finished_at` became required for the status `200` - the response property `detail` became required for the status `400` - the response property `detail` became required for the status `401` - the response property `detail` became required for the status `402` - the response property `detail` became required for the status `403` - the response property `detail` became required for the status `406` - the response property `detail` became required for the status `429` - the response property `detail` became required for the status `default` - the response property `errors` became required for the status `400` - …27 more - **2026-09-14** `8539cafd5cb6`: 2 breaking, 3 info - removed the required property `data/items/trigger_source` from the response with the `200` status - removed the required property `data/items/triggered_by` from the response with the `200` status - the endpoint scheme security `BearerAuth` was added to the API - the endpoint scheme security `LovableAPIKey` was added to the API - added the non-success response with the status `400` - **2026-09-11** `b19e0179b77a`: 1 info - api operation id `get-v1-projects-project_id-security-scans` removed and replaced with `listSecurityScans` - **2026-09-11** `c7f67a5564ac`: 1 breaking, 15 warning, 2 info - for the `query` request parameter `limit`, default value was changed from `20` to `50` - added the new `aikido_import` enum value to the `data/items/trigger_source` response property for the response status `200` - added the new `app_mcp_deep_auto` enum value to the `data/items/trigger_source` response property for the response status `200` - added the new `completed` enum value to the `data/items/status` response property for the response status `200` - added the new `enterprise_batch` enum value to the `data/items/trigger_source` response property for the response status `200` - added the new `failed` enum value to the `data/items/status` response property for the response status `200` - added the new `gitsync_pull` enum value to the `data/items/trigger_source` response property for the response status `200` - added the new `hvt_scheduled` enum value to the `data/items/trigger_source` response property for the response status `200` - added the new `manage_findings` enum value to the `data/items/trigger_source` response property for the response status `200` - added the new `running` enum value to the `data/items/status` response property for the response status `200` - added the new `system` enum value to the `data/items/triggered_by/type` response property for the response status `200` - added the new `ui_auto` enum value to the `data/items/trigger_source` response property for the response status `200` - added the new `user` enum value to the `data/items/trigger_source` response property for the response status `200` - added the new `user` enum value to the `data/items/triggered_by/type` response property for the response status `200` - added the new `workflow` enum value to the `data/items/trigger_source` response property for the response status `200` - added the new `workspace_scheduled` enum value to the `data/items/trigger_source` response property for the response status `200` - added the new optional `header` request parameter `Lovable-Beta` - added the new optional `header` request parameter `Lovable-Version` --- [Operation](https://skmtc.dev/lovable/apis/lovable-api/docs/v1/projects/:project_id/security-scans/get.md) - [API](https://skmtc.dev/lovable/apis/lovable-api.md) - [Page](https://skmtc.dev/lovable/apis/lovable-api/changes/v1/projects/:project_id/security-scans/get)