Listen to this article. Also available on Spotify. Subscribe to PolyAPI Squawk.
Managing a growing number of functions and resources and searching the public function catalog is a common challenge as environments expand. PolyAPI has introduced improvements to how API functions are searched and retrieved to address this. These updates focus on faster performance, better usability, and a simpler navigation experience across large functions.
The new search system adds two key enhancements: improved search functionality across API functions and pagination support for faster results loading. These updates make it easier for users to find the functions they need without delay, even in environments with thousands of entries.
How the New Search Works
Previously, searching through API functions could become slow, and developers often had to rely on basic browser tools like Ctrl + F to locate specific functions manually. The updated search functionality introduces a more efficient indexing system and improves querying by allowing filtering based on context and name fields. This makes narrowing down results and finding relevant functions easier without needing to scroll through long lists.
Pagination has also been introduced. Rather than attempting to load the full list of matching results at once, which could include potentially thousands of functions, PolyAPI now loads a limited set of results per page. Users can scroll or navigate through pages as needed. This improves performance by reducing the time required to display results and ensures a smoother experience when working in large environments.
An added benefit of the new search system is that the search term is now included in the URL. This allows developers to share filtered lists with others easily. For example, a user can generate and share a link that lists all OHIP functions related to profile management, helping teams collaborate more efficiently without repeating search steps manually.
Deprecation of Public Resource Pages
PolyAPI will begin deprecating the dedicated static pages listing public resources alongside the new search enhancements. In the past, developers could browse specific pages that listed all public functions or collections. While useful at smaller scales, this model does not scale efficiently as the number of public resources grows.
Users will be encouraged to use the improved search system to discover public resources. Public functions will still be accessible through dynamic search rather than fixed listings. A visibility filter has also been added, allowing users to choose whether to view environment-specific, tenant-wide, or public functions. This change improves consistency across private and public resource discovery, supports better filtering options, and ensures faster performance as the platform scales.
The transition will occur gradually. Specific public resource pages will be phased out over time, and users will be notified about any changes that affect access points.
Summary
For developers, the improved search experience means:
- Faster retrieval of function information, even in environments with a high number of resources
- More accurate and relevant search results based on better query processing
- Reduced loading times through pagination and dynamic result fetching
- A consistent method for finding both private and public API functions
- Easier sharing of filtered lists through URLs that include search terms
PolyAPI has updated its search functionality for API functions by adding improved indexing, better matching, and pagination for faster performance. The platform will also begin deprecating static public resource pages in favor of dynamic search. These changes support faster navigation, better resource discovery, and improved usability across private and public functions.
Want to see it in action? Reach out to us if you have any questions, or schedule a demo. You can also get started by creating an account, and setting up Poly on your own for free.