When fetching a single record via the API with the hydrated=true parameter, the response correctly includes the full public URLs for any files in Image/File fields. This is excellent.

However, when fetching a list of records, this hydration does not occur, even if the parameter were available. The API payload only contains the file token/ID, not the full URL.

This forces us to make a separate, secondary API call for each record in the list just to retrieve the image URL. This creates a classic "N+1 query problem," which is highly inefficient. It dramatically increases the number of API calls, slows down our applications, and consumes our API rate limit unnecessarily.

Proposed Solution:

Please extend the hydrated=true functionality to the "List Records" API endpoint. When this parameter is used, the Image and File field objects in the response for each record should include the full public URL, just as they do in the "Get Record" endpoint.

This change would significantly improve the performance and efficiency of any integration that needs to display or process images from multiple records at once (e.g., building galleries, generating reports, or syncing data to external systems).