@vincent Yeah, including the conversation ID can’t hurt. It would be more efficient than currently where you essentially have to hit another endpoint like Conversation.js to get the ID for a published URL.