Listen to this article. Also available on Spotify. Subscribe to PolyAPI Squawk.
Poly provides multiple levels of visibility for every primitive. Currently, we support environment, tenant, and public (instance-wide) visibility. In the future, we plan to introduce individual, team, and potentially global public (cross-instance) levels. Our vision includes a vast catalog of functions, variables, event handlers, and code snippets—growing from many thousands today to potentially tens of millions in the future.
To manage this scale, we implemented a system where every resource has a unique identifier (ID). Over time, we’ve expanded the use of these unique IDs across our platform to enhance usability and traceability.
Enhancements in Release 19
With Release 19, we introduced unique IDs for variables in generated libraries. This update significantly improves developers’ ability to:
- Troubleshoot more effectively – Unique IDs make it easier to reference specific resources when seeking assistance.
- Ensure accuracy in sensitive use cases – Developers can cross-check credentials to avoid errors.
- Hardcode references in Canopy and SDK generation – IDs allow precise resource specification when building UI apps, or when generating libraries.
The Future of Unique IDs
Looking ahead, we aim to make these IDs even more powerful by enabling:
- Intelligent notifications & monitoring – Automatically infer which resources are used in implementations.
- Improved resource ownership visibility – Help resource owners track usage and consumers identify owners for direct communication.
See for Yourself
To explore variable IDs, generate a library and check the definition files for variables. You’ll find unique IDs in comments and sub-functions.
Have questions about our roadmap or platform? We’d love to hear from you! Reach out to us at hello@polyapi.io, fill out a contact form or book an intro meeting.