# Feature request: non-strict (wildcard/regex) branch filtering on GET /builds

**URL:** <https://discuss.bitrise.io/t/feature-request-non-strict-wildcard-regex-branch-filtering-on-get-builds/25920>\
**Category:** Website\
**Tags:** api\
**Created:** [May 4, 2026, 2:36pm UTC](https://discuss.bitrise.io/t/feature-request-non-strict-wildcard-regex-branch-filtering-on-get-builds/25920 "2026-05-04T14:36:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![cyanoTest](https://avatars.discourse-cdn.com/v4/letter/c/ee7513/32.png) [@cyanoTest](https://discuss.bitrise.io/u/cyanoTest)\
**Post date:** [May 4, 2026, 2:36pm UTC](https://discuss.bitrise.io/t/feature-request-non-strict-wildcard-regex-branch-filtering-on-get-builds/25920/1 "2026-05-04T14:36:37Z")

</div>

Hi team,

I’d like to request a feature for the `GET /apps/{app-slug}/builds` endpoint (API v0.1).

**Current behavior** The `branch` query parameter only matches exact branch names. For example, `branch=development` works, but partial matching does not.

**Use case** Our branch naming convention is `/feature/{client}/{description}` (e.g. `/feature/acme/fix-login`, `/feature/acme/new-checkout`, etc.). We’d like to retrieve all builds for a given client without having to know every branch name in advance.

**Proposed enhancement** Add support for non-strict matching on the `branch` parameter, either via:

- wildcard syntax, e.g. `branch=/feature/acme/*`

- or a regex-based filter, e.g. `branch_pattern=^/feature/acme/.*`

If it’s not possible at least an endpoint to get all branches at once so we can filter on our side and make the strict filter/

Happy to provide more context if useful.

Thanks!