I can't imagine a reason NOT to add the list ID to the UI, especially considering how trivial it would be for you to do it. Here's a good reason why it should be there: Let's say I'm a developer, and I'm taking over a project where your API has been implemented to add users to a list when the user submits a form. Now the client has a new list and wants me to have users go to that list instead. I can clearly see where to update the list ID in the existing code, but what is the list ID of this new list??? You see, just because a developer is working with your API doesn't mean that developer has time to get to know your API, or has any good reason to. In this scenario, having the list ID available in the UI would save a developer time, and keep them from thinking bad thoughts about Constant Contact. You can simply add the ID as a data-id on the html element containing the list name, just as you've added your internal ID (I guess that's what that is) to the tr element. Developers will find that quickly. You don't have to change the look and feel of your UI.
... View more