GET/projects/{ProjectId}/configurations

Applies to QAComplete 14.5, last modified on August 06, 2024

Returns a list of configurations created in the specified QAComplete project.

Use the operation to get a list of all the configurations registered in a QAComplete project.

To get parameters of an individual configuration, use the …/configurations/{Id} (GET) operation.

Authentication

Basic authentication using a user’s login and password. See Authentication for details.

Security Rights

The authenticating user must belong to a security group that has the Read privilege for Test Library.

Request Format

To get information on configurations, send a GET request to the following URL:

http://{server}/rest-api/service/api/v2/projects/{ProjectId}/configurations?offset={offset}&limit={limit}&Filter={filter}

ProjectId  :  integer, required

The ID of the project.

offset  :  integer, default: 0

The number of configurations to skip before counting the returned configurations. The default value is 0, which is the offset of the first item. For details, see Paging Through Results Using Offset and Limit.

limit  :  integer, default: 25

The maximum number of configurations to return in the response.

filter  :  string

The filter expression to apply to the returned list. See Search Filters.

Note: If the filter expression you want to apply exceeds the maximum length of the request, or you want to get the expression from an external source, use the /projects/{ProjectId}/configurations/search (POST) operation instead.

A sample request:

GET http://yourserver.com/rest-api/service/api/v2/projects/11873/configurations HTTP/1.1
Host: yourserver.com
Connection: keep-alive
Accept: application/json
Authorization: Basic am9obkBleGFtcGxlLmNvbTpwQHNzd29yZA==

A sample request made by using cURL:

curl -u [email protected]:p@ssword -H "Accept: application/json" http://yourserver.com/service/api/v2/projects/11873/configurations

Response Format

On success, the operation responds with HTTP status code 200 and returns a JSON object with information about the configurations.

A sample response:

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 575


{
    "metadata": {
       "result_set": {
          "count": 1,
          "offset": 0,
          "limit": 25,
          "total": 1
       },
        "permissions": {
            "acl": 7
       }
    },
    "results": [
      {
        "id": 1,
        "folder_id": 0,
        "title": "IE9",
        "is_active": false,
        "create_user_id": 123456,
        "update_user_id": 123456,
        "date_created": "2016-08-31T09:13:59.9600000",
        "date_updated": "2016-08-31T09:13:59.9600000",
        "owner_user_id": 123456,
        "owner_name": "Smith, John ",
        "nbr_files_not_secured": 0,
        "user_name": "Smith, John ",
        "nbr_files": 0,
        "nbr_notes": 0,
        "original_id": 0,
        "import_id": 0,
        "project_id": 11873,
        "is_c_b_t": false,
        "custom_fields": [],
        "permissions": {
            "acl": 7
       }
      }
    ]
  }

Error responses

If the operation fails, it returns the appropriate status code and (optionally) the error description in the response body.

If the project with the specified ProjectId does not exist or the authenticating user does not have rights to access the project, the operation returns the Access is denied error.

See Also

Configurations Resources

Highlight search results