TestRail 10.10.0: Scale API retrieval and manage failed webhooks

TestRail 10.10.0 lets integration builders request up to 500 records per page and use cursor-based pagination on supported API list endpoints.

Larger API pages and cursor pagination

The limit parameter can now request up to 500 records for supported list endpoints. The default remains unchanged, so existing integrations retain their current page size.

Cursor pagination is available for get_cases, get_runs, get_results, get_results_for_run, get_tests, get_plans, get_milestones, get_sections, get_users, and get_projects. When more results exist, TestRail returns a _links.next URL. Cursor tokens expire after a period of time, and a stale token returns an error. Offset and cursor pagination cannot be mixed in the same traversal; sending both returns 400 Bad Request.

Compact API responses

Teams can request compact responses from list endpoints for cases, runs, suites, sections, plans, milestones, and results. This mode returns IDs, titles, statuses, relationships, and last-updated timestamps. It omits large custom fields, descriptions, attachments, and verbose metadata.

Webhook failure management and notifications

Webhook administrators can configure a webhook to remain active after consecutive delivery failures. The new toggle is in Administration > Integrations > Webhooks > Add/Edit. It is off by default, retaining the existing automatic-deactivation behavior.

When TestRail automatically deactivates a webhook, it sends email to its creator and all active administrators. The message includes the webhook name, endpoint URL, deactivation reason, timestamp, and next steps. Deactivation events are also recorded in Administration > Site Settings > Auditing. These additions support both Server and Cloud.

TestRail CLI 1.15.3

TestRail CLI 1.15.3 adds commands for reusable test data and configuration queries:

• variables manages reusable parameters referenced in test cases.
• datasets manages collections of variable values for test scenarios.
• groups views and manages groups and member lists.
• fields queries Dynamic Filter Fields.
• add_run and plans add now support Dynamic Filters.

Fixes and improvements

The release includes 61 fixes and improvements. Corrections cover bulk editing, BDD exports, storage reporting, user groups, shared steps, test case and test run saving, run ordering and dates, filtering, report and export output, attachments, large datasets, OAuth registration, OTP delivery, and API requests. The fixes also address failures when adding test-plan entries or uploading results from automation pipelines, plus an issue that could lock out non-admin users when a subscribed seat limit was reached.

What this means for your team

QA and automation engineers can use larger pages or cursor links when retrieving TestRail data, and compact responses where full record content is not required. This is great because teams using the CLI can manage variables and datasets or apply Dynamic Filters when creating runs and plan entries. QA managers now get email and audit visibility when automatic webhook deactivation occurs.

Based on the official TestRail release notes.

How Merito helps

Merito helps teams adopt and govern TestRail API, CLI, and webhook workflows through TestRail services, including practical integration and operating guidance.

Merito is an authorized TestRail reseller and services partner, listed as a Platinum Verified Partner in the TestRail partner directory. Our TestRail team helps you adopt the 10.10.0 changes, with implementation services to configure them for your environment and training and enablement to bring your teams up to speed.