Currently, each combination of engagement type and instance generates a unique API URL. This design prevents unexpected data from being mixed in — for example, if you create a test instance, that data won't accidentally flow into your production data feed. While this means you may need multiple URLs if you have multiple instances, the process is straightforward: generate each URL once using the dropdown-based tool, store them in a spreadsheet, and input them into your CRM or data aggregation system. Each URL is a one-time setup that then feeds data indefinitely. CUE is actively developing the ability to pull all instances of a single engagement type with one URL, which would reduce the number of URLs needed while still maintaining data integrity by keeping different engagement types separate.
