we’re building CI tooling on top of the Testiny REST API that lets our QA team trigger automation runs for a specific Testcase Folder subtree. Pulling test cases via POST /api/v1/testcase/find with
resultFilter.testcase_folder_parent_id: {“op”: “in_subtree_or_self”, “value”: } already works perfectly.
To build the folder selection, we need a way to list the complete folder tree (id, title, parent folder) — including folders that have no test case assigned directly to them, only via subfolders. Your documentation
( Quickstart for Testiny REST API | Testiny Documentation ) describes the following endpoints for the testcase_folder entity, but all three return 404 API_ROUTE_NOT_FOUND on our account:
- POST /api/v1/testcase_folder/find
- GET /api/v1/testcase_folder/{id}
- GET /api/v1/testcase_folder
Example error response:
{“type”:“ApiError”,“code”:“API_ROUTE_NOT_FOUND”,“message”:“Api route to ‘GET’ for ‘/testcase_folder’ not found”}
Could you either:
- enable/fix these endpoints for our account, or
- tell us the correct way to fetch the complete folder tree (including folders with no directly assigned test cases)?
Currently, the only way to determine a folder’s title is via the testcase_folder join on /testcase/find — but that only returns folders that have at least one test case assigned to them directly. Purely organizational “grouping
folders” (which only contain subfolders) remain invisible this way, even though we can already query test cases in their subtree without any problem.
Thank you very much!
