/revisions/{locator}/list-dependencies

Retrieve dependencies for a given revision using the V1 legacy API format. This is a POST version of the GET /api/revisions/:locator/dependencies endpoint that accepts parameters in the request body instead of query parameters. This allows for larger payloads that would exceed URI/header size limits when using query parameters (e.g., when filtering by a large list of locators).

Note: This endpoint returns the V1 legacy format with streaming JSON array output. For new integrations, consider using the V2 API at GET /v2/revisions/{locator}/dependencies which returns a paginated response with a cleaner data structure.

The endpoint returns a streaming JSON array of dependencies with detailed information including the DependencyLock, full license objects, issueTargets, and legacy metadata fields.

Path Params
string
required

The URL-encoded locator of the revision

Body Params

Query parameters for filtering and configuring the dependency response

integer
1 to 10000

Maximum number of dependencies to return (min 1, max 10000)

integer
≥ 0

Number of dependencies to skip for pagination

boolean
Defaults to false

Whether to include ignored dependencies in the response

boolean
Defaults to false

Whether to include hash and version data for dependencies

boolean
Defaults to false

Whether to include full license text in the license information

includeLocators
array of strings

Array of locators to filter dependencies. Only dependencies matching these locators will be returned

includeLocators
Responses

Language
Credentials
Bearer
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json