Skip to main content

Reminder - Poly Lens Insights Feed and API Changes Take Effect Tomorrow

The updates outlined in our August announcement take effect tomorrow, November 3, 2026. Here’s what’s changing and what you need to review if you maintain an integration with the Poly Lens GraphQL API.

What’s Changing​

The Poly Lens Insights Feed will reach end of life. Beginning tomorrow, the feed will no longer be accessible, and automatically generated insight cards will no longer appear.
A new homepage tile will replace the Insights Feed. The card displays each user’s most recently viewed pages, making it easier to return to pages they’ve visited.

Analytics and Reporting Remain Available​

You can continue to access:

  • Historical and trend analytics on the Device, Room, and Site Overview pages under Analytics
  • The Device and Room Insights Dashboard under Insights > Dashboard
  • Historical reports under Insights > Reports

These tools remain available to help you understand device activity, room utilization, meeting behavior, and trends across your environment.

Required Updates for API Integrations​

The following GraphQL queries will be deprecated on November 3rd:

  • topics
  • insightsPriority
  • topicIndicators
  • charts

The topics, insightsPriority, and topicIndicators queries have no replacements. Remove dependencies on these queries from your integrations.

For charts, migrate from the root-level query to the analytics field on the Tenant, Site, Room, or Device object, depending on the scope of data you need.

Within analytics, select the metric fields your integration requires and supply their required arguments. This migration requires updating your query structure and field selections, rather than simply renaming charts to analytics. Available metrics, arguments, and response types vary by object.

Use the schema explorer in the Poly Lens API Playground to review the relevant fields and validate your updated queries before the changes take effect.

If you do not use any of the affected queries, no integration changes are required.