Mend API (3.0.1)

Enter the page number to display in the result. Page numbers start at 0

Filter your search to return items whose property has a specific value. Use the syntax: property:operation:value where a colon (:) separates between property, operation and value.

• Property: the name of the property of the item
• Operation:
  • between - true if the value is inside a range. Syntax: lowest value comma (,) highest value. E.g. between:2019-05-01,2019-06-01
  • equals - true if the value is identical to this value.
  • gt - true if the value is greater than this value.
  • in - true if the value is identical to one of the items in this comma-separated list. E.g. in:value1,value2,value3
  • like - true if the property's value is contained within this value
  • regex - true if this regular expression resolves as true. The regex is not case sensitive, and special characters must be escaped with a backslash. Special characters can be space, double quote ("), '<', '>', '#', '%', '{', '}', vertical bar ('|'), backslash, '^'. To pass an escaped character in a URL in Postman, encode it first. E.g. to return all items whose value begins with a or A, use regex:^a
• Value: the value of the property.

To combine multiple filters, separate each filter with a semicolon with no space. E.g. property1:operation1:value1;property2:operation2:value2

This endpoint supports filtering on the following properties and its supported operators:

• comment:[like | equals | regex]:value
• commentBy:[like | equals | regex]:value
• componentName:[like | equals | regex]:value
• criticalNum:gt:value
• detectedAt:between:date1,date2. E.g. between:2019-05-01,2019-06-01
• directDependency:equals:value
• effective:[like | in | equals | regex]:value
• hasFix:equals:value
• highNum:gt:value
• lastCveUpdatedAt:between:date1,date2. E.g. between:2019-05-01,2019-06-01
• lowNum:gt:value
• mediumNum:gt:value
• modifiedAt:between:date1,date2. E.g. between:2019-05-01,2019-06-01
• projectName:[like | equals | regex]:value
• publishedAt:between:date1,date2. E.g. between:2019-05-01,2019-06-01
• score:between:lowvalue,highvalue
• scoreType:[like | equals | regex]:value
• severity:[like | equals | regex]:value
• sourceFileName:[like | equals | regex]:value
• status:[in | equals]:value
• vulnerabilityName:[like | equals | regex]:value
• vulnerabilityType:[equals | in]:value

Sort search results alphabetically on an item's property by entering sort= followed by the property name. E.g. enter sort=email to sort alphabetically by their email addresses from a-z ascending.To sort in descending order (z-a), add a minus sign ('-'). E.g. sort=-email.

You can sort by the following properties:

• comment
• commentUserName
• componentName
• detectedAt
• directDependency
• effective
• highNum
• lastCveUpdatedAt
• lowNum
• mediumNum
• modifiedAt
• projectName
• publishedAt
• score
• scoreType
• severity
• status
• vulnerabilityName
• vulnerabilityType
• weight

Enter the page number to display in the result. Page numbers start at 0

Filter your search to return items whose property has a specific value. Use the syntax: property:operation:value where a colon (:) separates between property, operation and value.

• Property: the name of the property of the item
• Operation:
  • between - true if the value is inside a range. Syntax: lowest value comma (,) highest value. E.g. between:2019-05-01,2019-06-01
  • equals - true if the value is identical to this value.
  • gt - true if the value is greater than this value.
  • in - true if the value is identical to one of the items in this comma-separated list. E.g. in:value1,value2,value3
  • like - true if the property's value is contained within this value
  • regex - true if this regular expression resolves as true. The regex is not case sensitive, and special characters must be escaped with a backslash. Special characters include space, double quote ("), '<', '>', '#', '%', '{', '}', vertical bar ('|'), backslash, '^'. To pass an escaped character in a URL in Postman, encode it first. E.g. to return all items whose value begins with a or A, use regex:^a
• Value: the value of the property.

To combine multiple filters, separate each filter with a semicolon with no space. E.g. property1:operation1:value1;property2:operation2:value2

This endpoint supports filtering on the following properties and its supported operators:

• comment:[like | equals | regex]:value
• commentUserEmail:[like | equals | regex]:value
• componentName:[like | equals | regex]:value
• detectedAt:between:date1,date2. E.g. between:2019-05-01,2019-06-01
• directDependency:equals:value
• effective:[like | equals | regex | in]:value
• hasFix:equals:value
• lastCveUpdatedAt:between:date1,date2. E.g. between:2019-05-01,2019-06-01
• modifiedAt:between:date1,date2. E.g. between:2019-05-01,2019-06-01
• projectName:[like | equals | regex]:value
• score:between:lowvalue,highvalue
• scoreType:[like | equals | regex]:value
• severity:[like | equals | regex]:value
• sourceFileName:[like | equals | regex]:value
• status:[in | equals]:value
• vulnerabilityName:[like | equals | regex]:value
• vulnerabilityType:[equals | in]:value
• libraryType:[equals | in | like | regex]:value

Sort search results alphabetically on an item's property by entering sort= followed by the property name. E.g. enter sort=email to sort alphabetically by their email addresses from a-z ascending.To sort in descending order (z-a), add a minus sign ('-'). E.g. sort=-email.

You can sort by the following properties:

• comment
• commentUserEmail
• componentName
• detectedAt
• directDependency
• effective
• hasFix
• lastCveUpdatedAt
• modifiedAt
• projectName
• score
• scoreType
• severity
• sourceFileName
• status
• vulnerabilityName
• vulnerabilityType
• libraryType

Used to add alert integration and library location information

Enter the page number to display in the result. Page numbers start at 0

Filter your search to return items whose property has a specific value. Use the syntax: property:operation:value where a colon (:) separates between property, operation and value.

• Property: the name of the property of the item
• Operation:
  • between - true if the value is inside a range. Syntax: lowest value comma (,) highest value. E.g. between:2019-05-01,2019-06-01
  • equals - true if the value is identical to this value.
  • gt - true if the value is greater than this value.
  • in - true if the value is identical to one of the items in this comma-separated list. E.g. in:value1,value2,value3
  • like - true if the property's value is contained within this value
  • regex - true if this regular expression resolves as true. The regex is not case sensitive, and special characters must be escaped with a backslash. Special characters include space, double quote ("), '<', '>', '#', '%', '{', '}', vertical bar ('|'), backslash, '^'. To pass an escaped character in a URL in Postman, encode it first. E.g. to return all items whose value begins with a or A, use regex:^a
• Value: the value of the property.

To combine multiple filters, separate each filter with a semicolon with no space. E.g. property1:operation1:value1;property2:operation2:value2

This endpoint supports filtering on the following properties and its supported operators:

• availableVersion:equals:value
• availableVersionType:[equals | in]:value
• comment:[like | equals | regex]:value
• commentUserEmail:[like | equals | regex]:value
• componentName:[like | equals | regex]:value
• componentType:[equals | in]:value
• detectedAt:between:date1,date2. E.g. between:2019-05-01,2019-06-01
• license:[like | regex ]:value
• modifiedAt:between:date1,date2. E.g. between:2019-05-01,2019-06-01
• numberOfLicenses:[gt | equals]:value
• policyName:[like | equals | regex]:value
• projectName:[like | equals | regex]:value
• status:[in | equals]:value
• type:[equals | in]:value

Sort search results alphabetically on an item's property by entering sort= followed by the property name. E.g. enter sort=email to sort alphabetically by their email addresses from a-z ascending.To sort in descending order (z-a), add a minus sign ('-'). E.g. sort=-email.

You can sort by the following properties:

• availableVersionType
• comment
• componentName
• componentType
• detectedAt
• modifiedAt
• numberOfLicenses
• policyName
• status
• type
• versionType