Building a mobile Frame.io client, we render the project’s shares list with filter chips (All / Active / Passphrase-protected / Expired) and a search box over share names. Two related gaps below.
1. Filtering
GET /v4/accounts/{account_id}/projects/{project_id}/shares only accepts sort, after, page_size and include_total_count, so none of the filter chips can be asked of the server. The workaround - filtering client-side over already-fetched pages - is only honest for small projects: a user filtering by “Expired” sees expired shares among the pages loaded so far, not all of them. Fetching every page before applying a filter is not viable on projects with many shares.
Requested: filter[enabled], filter[access], filter[has_passphrase], and a range filter on expiration (e.g. filter[expiration_before] / filter[expiration_after]).
2. Search
The same screen needs a search action over share names. List shares has no q/qsearch parameter, and POST /v4/accounts/{account_id}/search appears to be aimed at assets and transcriptions rather than shares.
Requested: either a q parameter on the shares listing, or explicit support for shares as a resource type in the search endpoint (and a line in the docs clarifying this - today it’s ambiguous).
Related threads that touch on adjacent filtering/search needs: Search, filter, and sort by tags and Is there a way to list assets based on metadata, or collections as filter?.