Pagination
When a REST API response contains a large number of test cases or test runs, the results are paginated to enhance manageability and performance. By default, you will receive 30 test cases or test runs per page. This document outlines how to navigate through paginated results.
Pagination using page numbers
By default, the first page is listed. To navigate through pages, use the p parameter in the request parameters to load the specific page you want to view.
Note: You can select a page size of either
30or300while using the parameterpage_size.
An example request with query parameter.
Request Parameters
Request
curl -u "YOUR_USERNAME:YOUR_ACCESS_KEY" \
https://test-management.browserstack.com/api/v2/projects/PR-1/test-case?p=3
-
project_id* String
Identifier of the project.
-
test_case_id String
Identifier of the test case, used as a query parameter.
-
created_after String
Fetch test cases created after this timestamp. (e.g.,
YYYY-MM-DDTHH:MM:SS.SSSZ). -
created_before String
Fetch test cases created before this timestamp. (e.g.,
YYYY-MM-DDTHH:MM:SS.SSSZ). -
issue_ids String
Comma-separated list of issue IDs to filter test cases (e.g.
TM-123,TES-456,IS-789). -
issue_type String
Set to
jirawhen filtering byissue_ids.
How do I know if there are more pages?
The pagination information will be included at the end of the API response under info. If the next parameter is set to null, you are on the last page of the results.
Response Attributes
Response
"info": {
"page": 3,
"page_size": 30,
"count": 82,
"prev": 2,
"next": null
}
-
page integer
Current page number.
-
page_size integer
Fixed Number of records you will receive per page in API response.
-
count integer
Total number of records across all pages.
-
prev integer
Previous page number.
-
next integer
Next page number.
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.