Trying this and many body variants (which all return the same):
POST /api/v2/conversations/emails/2cf1d8f5-c1ce-44d5-9253-d9f171595bc2/messages/draft/attachments/copy HTTP/1.1
Host: api.mypurecloud.com
Authorization: Bearer *******************
Content-Type: application/json
I think I've found the issue. The conversation id has to be for the existing conversation, not a new one.
The sourceMessage id is the entity id in
/api/v2/conversations/emails/{conversationId}/messages request. So this looks to be for adding old attachments to a reconnect or similar.
This unfortunately doesn't fix our problem. GC has a limitation of 30 days for reconnects and the customer needs a 90 day limit. We were hoping to create a new email and copy the old attachments across.
How are you doing?
I work for the company Cloudoe and we provide this functionality"out of the box" in our AMI - Advanced eMail Interface services. I show you the example in this video. Uploading
Let me know if you're interested in discussing this further -