For the complete documentation index, see llms.txt. This page is also available as Markdown.

Projects

Create and list projects, and query project components

Add private image configuration

post

Add a configuration with a name and description. Provide the registry ID and access key for the private application. The returned configurationId is used to add projects (repositories).

Authorizations
AuthorizationstringRequired

Use the accessToken returned by the login endpoint as a Bearer token.

Body
namestringRequiredExample: <configuration-name>
descriptionstringRequiredExample: <configuration-description>
registryIdstringRequired

AWS account ID

Example: <aws account id>
accessKeystringRequiredExample: <access key>
secretKeystringRequiredExample: <aws secret key>
regionstringRequired

AWS ECR region

Example: <aws ecr region>
Responses
201

Configuration saved successfully.

application/json
post/integrations/image/api/v1/aws/configuration/save
201

Configuration saved successfully.

Add private image project

post

Add a private image project (repository) using the configurationId returned by the configuration/save call.

Authorizations
AuthorizationstringRequired

Use the accessToken returned by the login endpoint as a Bearer token.

Body
configurationIdintegerRequiredExample: 1700
Responses
201

Repositories saved successfully.

application/json
post/integrations/image/api/v1/aws/configuration/repository
201

Repositories saved successfully.

List projects

get

List projects for the authenticated tenant. Requires the Bearer access token from the login prerequisite. REVIEW: In the source PDF this request also sends a separate "token" header whose value duplicates the access token. It is included below as an optional header; confirm whether it is actually required.

Authorizations
AuthorizationstringRequired

Use the accessToken returned by the login endpoint as a Bearer token.

Query parameters
pageintegerOptionalDefault: 0Example: 0
sizeintegerOptionalDefault: 2000Example: 2000
projectFilterstringOptional
timestampintegerOptionalExample: 120
Header parameters
tokenstringOptional

REVIEW: Duplicates the Bearer access token in the source PDF.

Responses
200

Project list.

application/json
total_countintegerOptionalExample: 17
current_pageintegerOptionalExample: 0
total_pagesintegerOptionalExample: 0
page_sizeintegerOptionalExample: 2000
get/scim/api/v2/projects/
200

Project list.

List project components using LQL

post

Query a project's components with Lineaje Query Language (LQL). Run this once the project's job status is "Ready for review". Requires the Bearer access token from the login prerequisite and the sbom_id from the project list. This is one LQL example; for the full set of queries and use cases see the LQL documentation linked under externalDocs. REVIEW (per Mudit, 2026-06-23): replace the LQL documentation link with the published URL once available (draft expected end of day 2026-06-23).

Authorizations
AuthorizationstringRequired

Use the accessToken returned by the login endpoint as a Bearer token.

Body
lqlstringRequired

Lineaje Query Language statement. Substitute <sbom_id> with the project's sbom_id.

Example: project.id=<sbom_id> $and vulnerability.severity=all $and code_quality.severity=all $and security_posture.severity=all $and provenance.country.code = all $and source_code.languages=all| stats count(project.id)
limitintegerOptionalExample: 1
valueschemastringOptionalExample: componentSchema
product_idintegerOptionalExample: 1
Responses
200

Component query result. The top-level key is the LQL query string and its value is an array of component objects.

application/json

The single top-level property is the LQL query string; its value is an array of component objects. Modeled as a free-form object because the key is dynamic. See the example for the full shape returned by the API.

Other propertiesanyOptional
post/api/v1/lql/components
200

Component query result. The top-level key is the LQL query string and its value is an array of component objects.

Last updated