Teams that manage multiple Displayr projects programmatically — for example, creating one project per wave per brand via the API — have no way to query or discover existing projects under their company account through the API. This makes it difficult to check whether a project already exists before creating a new one, look up a project by a known identifier (such as a wave ID), or maintain an accurate registry of projects without building and maintaining a separate tracking system outside of Displayr.

The current workaround requires capturing and storing document secrets at creation time, or manually retrieving them from the Displayr UI for any pre-existing projects. For teams operating at scale with many projects, this creates operational overhead and risk — if the external registry falls out of sync or a project was created outside the normal process, there is no way to reconcile it programmatically.