API for Requirement

API for Requirement

Starting March 2026 with QMetry Test Management version 8.25.0, the documentation was migrated from Atlassian to a dedicated, standalone QMetry Test Management documentation site. For the latest updates, refer to API for Requirement.

POST /rest/requirements/list/viewColumns

Description

Fetch data of Requirements along with custom fields. Returns data from latest version.

Request

Content-Type: application/json

Parameters

Name

Located in

Required

Description

Default

Schema

Name

Located in

Required

Description

Default

Schema

viewId

body

yes

View ID of the user for that particular project and Requirement module. View ID can be fetched from latestViews section of Getinfo API.

-

integer

folderPath

body

yes

Path of folder whose Requirements are to be fetched

-

string

start

body

no

Start index of records

-

integer

limit

body

no

Number of records per page

-

integer

page

body

no

Page number to be displayed

-

integer

Response

Content-Type: application/json

Status Code

Reason

Response Model

Status Code

Reason

Response Model

200

Requirement list fetched successfully

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-

POST /rest/requirements/list

Description

Get details of a requirement by providing ID of requirement, requirement version ID or requirement folder.

Request

Content-Type: application/json

Parameters

Name

Located in

Required

Description

Default

Schema

Name

Located in

Required

Description

Default

Schema

start

body

no

Start index of records

-

integer

limit

body

no

Number of records per page

-

integer

page

body

no

Page number to be displayed

-

integer

id

body

yes

Id of Requirement

-

integer

filter

body

no

Filter to be applied

-

string

Response

Content-Type:application/json

Status Code

Reason

Response Model

Status Code

Reason

Response Model

200

Requirement list fetch successfully

ResponseEntityString

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-

POST /rest/requirements/getVersionDetail

Request

Content-Type: application/json

Parameters

Parameters

Name

Located in

Required

Description

Default

Schema

Name

Located in

Required

Description

Default

Schema

rqID

body

yes

Id of Requirement

-

integer

start

body

no

Start index of records

-

integer

limit

body

no

Number of records per page

-

integer

page

body

no

Page number to be displayed

-

integer

Response

Content-Type: application/json

Status Code

Reason

Response Model

Status Code

Reason

Response Model

200

Requirement version detail list fetch successfully.

ResponseEntity

400

Invalid json object or mandatory fields missing

-