Interesting update! Being able to read custom field values for multiple clients in a single API request can really simplify workflows and reduce unnecessary calls. While looking into related public information resources I also found https://mainecourtrecords.org useful for exploring court data. Improvements like this make managing and accessing information much more efficient.

Great suggestion for reducing the number of API requests when working with multiple clients. I’ve found that organizing related reference data including https://sedgwickcountycourts.org can also make integrations easier to manage and verify. A single, well-structured request often improves both performance and maintenance. Thanks for sharing such a practical approach.

Yes, as a developer, we have received a lot of requests from our clients to include the custom field in our app, as they store information they need in this field. However, reading it on a per‑client basis is quite impractical, as we would need to retrieve the value for every single client in the database at all times for our clients.

Yes! This!

With the introduction of the Paged Client List perhaps we can introduce Detailed response and it include the custom fields for just those clients in the page.