Currently, Port's FireHydrant integration fetches the full dataset (e.g., all incidents) from the FireHydrant API before applying the mapping selector.query (JQ filter) on Port's side [Default mapping configuration]. For organizations with a high volume of historical incidents, fetching thousands of records when only a small subset is needed leads to inefficient syncs, increased ingestion time, and unnecessary API load

We request the ability to pass query parameters / pre-filters directly to the FireHydrant API (e.g., similar to apiQueryParams or native API filters supported in other integrations) so that only relevant data is fetched during syncs

Fetching thousands of unneeded records creates excessive network overhead, slows down catalog resyncs, and risks hitting upstream rate limits