How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Mend Dependencies Source Files API

The Dependencies Source Files API from Mend — 8 operation(s) for dependencies source files.

Mend Dependencies Source Files API is one of 47 APIs that Mend publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Dependencies Source Files. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 8 operations across 8 paths, and defines 19 schemas. It is described by OpenAPI 3.0.1, at version 3.0.

Requests are made against a single base URL, https://baseUrl.

8 operations 8 paths 19 schemas 4 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
3.0
Base URL
https://api-saas.mend.io
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Mend Dependencies Source Files API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearer-key). By default, every request must be authenticated.

  • bearer-key — JWT token Bearer

Paths & Operations 8

Across 8 paths, the API surfaces 8 operations — 4 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Dependencies Source Files 8
GET
/api/v3.0/projects/{projectUuid}/dependencies/sourceFiles/inventory
Get source files inventory at project level
getSourceFilesInventoryProject 3 params → 200400403
POST
/api/v3.0/projects/{projectUuid}/dependencies/sourceFiles/matchSuggestions
Get Mend library suggestions for source files at project level
getMatchSuggestionsProject 1 param body → 200400403
GET
/api/v3.0/projects/{projectUuid}/dependencies/sourceFiles/searchForMatch
Search for library matches for source files at project level
searchForMatchProject 1 param → 200400403
GET
/api/v3.0/applications/{applicationUuid}/dependencies/sourceFiles/inventory
Get source files inventory at application level
getSourceFilesInventoryApplication 3 params → 200400403
POST
/api/v3.0/applications/{applicationUuid}/dependencies/sourceFiles/matchSuggestions
Get Mend library suggestions for source files at application level
getMatchSuggestionsApplication 1 param body → 200400403
GET
/api/v3.0/applications/{applicationUuid}/dependencies/sourceFiles/searchForMatch
Search for library matches for source files at application level
searchForMatchApplication 1 param → 200400403
POST
/api/v3.0/orgs/{orgUuid}/applications/dependencies/sourceFiles/remapping
Remap source files at application level
remapSourceFilesApplication 1 param body → 202400403404
POST
/api/v3.0/orgs/{orgUuid}/dependencies/sourceFiles/remapping
Remap source files at organization level
remapSourceFilesOrganization 1 param body → 202400403404

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are SourceFileInventoryDTOV3 (10 properties), SourceLibraryResponseDTO_SearchForMatch (9 properties), SourceLibraryResponseDTO_MatchSuggestions (9 properties), LicenseProfileDTO (9 properties). Each schema is shown below with its type and property counts.

LiteLicenseDTO_MatchSuggestions
object
Collection of licenses associated with this library
2 properties 1 required
RiskScoreExplanationDTO
object
3 properties
SourceFileLibraryDTO
object
4 properties
SourceFilesRemappingAsyncStatusDtoV3
object
Async process status for source file remapping operations
4 properties
DWRResponsePageableV3CollectionSourceFileInventoryDTOV3
object
3 properties
SourceFileInventoryDTOV3
object
10 properties
LicenseProfileDTO
object
9 properties
LiteLicenseDTO_SearchForMatch
object
Collection of licenses associated with this library
2 properties 1 required
SourceFileRemappingAppRequestDTOV3
object
Request payload for remapping source files at application level
6 properties
LibraryMatchSuggestionsRequestDTOV3_MatchSuggestions
object
Request payload for retrieving Mend library suggestions for source files. Requires sourceFileUuids and recommendedForAllFiles. Medium privilege users can optio…
2 properties 2 required
ProjectDTOV3
object
Project information
5 properties
DWRResponseV3CollectionSourceLibraryResponseDTO_MatchSuggestions
object
2 properties
DWRResponseBase
object
1 property
SourceFileRemappingOrgRequestDTOV3
object
Request payload for remapping source files at organization level
5 properties
SourceLibraryResponseDTO_SearchForMatch
object
Library match suggestion response containing library details and match metadata
9 properties
LicenseDTO
object
7 properties 1 required
SourceLibraryResponseDTO_MatchSuggestions
object
Library match suggestion response containing library details and match metadata
9 properties
DescriptionAndExplanationDTO
object
4 properties
DWRResponseV3CollectionSourceLibraryResponseDTO_SearchForMatch
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mend-dependencies-source-files-api-openapi.yml Raw ↑

Other APIs Mend publishes across the network.

Mend Access Management API
Mend Access Management - Organizations API
Mend Administration - Groups API
Mend Administration - Labels API
Mend Administration - Users API
Mend AI API
Mend Alerts - Product API
Mend Alerts - Project API
Mend Applications API
Mend Asynchronous Process Control API
Mend CustomAttribute - Organization API
Mend CustomAttribute - Product API
Where this information came from

This is an independent, third-party profile of Mend Dependencies Source Files API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.