In-app (click able links) to conversations provided by API responses

you should put the conversation id in the response of the create draft endpoint (and other endpoint like create message) directly. I had to extract it out of the url `_links.related.conversation`. It would have been better to extract it out of the path `conversation.id`

Easily able to be constructed with the /open url by user but passing along the feedback/request nonetheless. Likely 'will not do'. Currently, conversation links provided in response are API specific resources to be used by fetching.

Request