Right now we can create a list, add items, remove items, unbind/bind it from campaigns, even delete it — all without a campaign ID. But if we just want to see the records in that list, the API makes me bind it to a campaign first.
The UI already shows list contents when the list isn’t tied to a campaign, so why not the API too? It feels inconsistent.
The way it works today, we end up creating “fake” campaigns just to grab the data. That clutters the environment and sometimes even caused our lists to get out of sync. For us, these unbound lists are mostly test lists we use for staging, validation, and troubleshooting.
What would be great:
-
An endpoint like
getRecordsByListId
that just returns the list as-is, no campaign data attached. -
Optional CSV export with delimiter choice (comma, semicolon, tab) and column selection. If CSV is picked, just dump the whole list in one shot.
Priority:
-
Dev side: high (makes life easier, avoids hacks).
-
Business side: routine (not breaking anything, just smoother and less error-prone).
Basically: if we can add and delete records from a list without a campaign, we should also be able to pull those records the same way.