curl --request GET \
--url https://api.testdino.com/api/public/v1/{projectId}/filters \
--header 'Authorization: Bearer <token>'{
"success": true,
"data": {
"environments": [
{
"environment": "<string>",
"authors": [
{
"author": "<string>",
"branches": [
"<string>"
]
}
]
}
],
"testRunTags": [
"<string>"
],
"testCaseTags": [
"<string>"
]
}
}Distinct filter values available for this project.
Returns environments, branches per environment, developers (git authors) per environment, run-level tags, and test case tags. Use it to populate filter dropdowns, tag selectors, and developer pickers — scope via dateRange or startDate/endDate (tags are returned across all time).
curl --request GET \
--url https://api.testdino.com/api/public/v1/{projectId}/filters \
--header 'Authorization: Bearer <token>'{
"success": true,
"data": {
"environments": [
{
"environment": "<string>",
"authors": [
{
"author": "<string>",
"branches": [
"<string>"
]
}
]
}
],
"testRunTags": [
"<string>"
],
"testCaseTags": [
"<string>"
]
}
}Project PAT (tdp_) token with public-api scope
The project identifier (e.g. project_abc123). Must match the project associated with your PAT.
Predefined date range filter. Takes precedence over startDate/endDate if both are provided. For custom ranges, omit this and use startDate+endDate instead.
7d, 14d, 30d, 60d, 90d Filter results by environment name (e.g. production, staging). Use the /filters endpoint to discover available environments.
Start of a custom date range (ISO 8601 date, e.g. 2026-03-01). Must be used together with endDate. Ignored if dateRange is also provided.
End of a custom date range (ISO 8601 date, e.g. 2026-03-31). Must be used together with startDate. Ignored if dateRange is also provided.
Was this page helpful?