> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scanoss.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get transitive dependency details



## OpenAPI

````yaml /api-reference/dependencies-openapi.json post /v2/dependencies/transitive/components
openapi: 3.0.0
info:
  title: SCANOSS Dependency Service
  version: '2.0'
  contact:
    name: scanoss-dependencies
    url: https://github.com/scanoss/dependencies
    email: support@scanoss.com
servers: []
security: []
tags:
  - name: Dependencies
paths:
  /v2/dependencies/transitive/components:
    post:
      tags:
        - Dependencies
      summary: Get transitive dependency details
      operationId: Dependencies_GetTransitiveDependencies
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/v2TransitiveDependencyRequest'
        required: true
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/v2TransitiveDependencyResponse'
        '404':
          description: Returned when the resource does not exist.
          content:
            application/json:
              schema:
                type: string
                format: string
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/rpcStatus'
components:
  schemas:
    v2TransitiveDependencyRequest:
      type: object
      example:
        depth: 3
        limit: 50
        components:
          - purl: pkg:npm/express
            requirement: 4.18.0
          - purl: pkg:npm/lodash
            requirement: 4.17.0
      properties:
        depth:
          type: integer
          format: int32
          title: >-
            Depth (number of layers) to go when searching for dependencies -
            optional
        limit:
          type: integer
          format: int32
          description: >-
            TODO: Add scope filters:

            repeated string scope_include

            repeated string scope_exclude

            Using a list of strings allows filtering by multiple scopes
            simultaneously

            (e.g., include both "dev" and "test" dependencies in a single
            request)
          title: Limit the number of components reported back - optional
        components:
          type: array
          items:
            $ref: '#/components/schemas/v2ComponentRequest'
          title: |-
            List of Purls from the same ecosystem
            Supported ecosystems: "composer", "crates", "maven", "npm", "gem"
      title: Transitive dependency request data (JSON payload)
    v2TransitiveDependencyResponse:
      type: object
      example:
        dependencies:
          - purl: pkg:npm/express@4.18.2
            version: 4.18.2
          - purl: pkg:npm/body-parser@1.20.1
            version: 1.20.1
          - purl: pkg:npm/cookie@0.5.0
            version: 0.5.0
        status:
          status: SUCCESS
          message: Transitive dependencies successfully retrieved
      properties:
        dependencies:
          type: array
          items:
            $ref: '#/components/schemas/TransitiveDependencyResponseComponent'
          title: Dependency response details
        status:
          $ref: '#/components/schemas/v2StatusResponse'
      title: Transitive dependency response data (JSON payload)
    rpcStatus:
      type: object
      properties:
        code:
          type: integer
          format: int32
        message:
          type: string
        details:
          type: array
          items:
            $ref: '#/components/schemas/protobufAny'
    v2ComponentRequest:
      type: object
      example:
        purl: pkg:github/scanoss/engine@1.0.0
      properties:
        purl:
          type: string
          description: Package URL identifying the component to analyze.
        requirement:
          type: string
          description: >-
            Version constraint for component resolution when PURL lacks explicit
            version.
      description: >-
        Represents a software component to be analyzed by SCANOSS API services.

        Combines a Package URL for component identification with optional
        version constraints for resolution.
      required:
        - purl
    TransitiveDependencyResponseComponent:
      type: object
      properties:
        purl:
          type: string
        version:
          type: string
        requirement:
          type: string
          title: 'optional string scope = 3; // TODO: Add scope field'
    v2StatusResponse:
      type: object
      properties:
        status:
          $ref: '#/components/schemas/v2StatusCode'
        message:
          type: string
          title: Status message
        db:
          $ref: '#/components/schemas/StatusResponseDB'
        server:
          $ref: '#/components/schemas/StatusResponseServer'
      description: Detailed response details.
    protobufAny:
      type: object
      properties:
        '@type':
          type: string
      additionalProperties: {}
    v2StatusCode:
      type: string
      enum:
        - UNSPECIFIED
        - SUCCESS
        - SUCCEEDED_WITH_WARNINGS
        - WARNING
        - FAILED
      default: UNSPECIFIED
      description: Status code Enum.
    StatusResponseDB:
      type: object
      properties:
        schema_version:
          type: string
          title: Semantic schema version (e.g., 'v1.0.0')
        created_at:
          type: string
          title: When this DB was built (ISO 8601 format)
      description: Database version information.
    StatusResponseServer:
      type: object
      properties:
        version:
          type: string
          title: Semantic version (e.g., 'v1.0.0')
      description: Server information.

````