A developer writes:
Ive been working on a piece of software and I have a request..
https://developer.ringcentral.com/api-docs/latest/index.html#!#RefUpdateMessage.html
I have not tested it.. but I was hoping instead of submitting the following
{readStatus: Read}
Submit
{Extension: $NewExtension}
which will result in Forwarding the message to another extension.
Unfortunately we cannot support it this way. There are different types of messages (Voicemails, Faxes, SMS, etc.) and not all of them can be really forwarded, so we cannot add this capability in our general message-store API. Another reason is that forwarding will create a new message, but just the content will be cloned. And this is not what is usually expected by calling PUT in the RESTful API world (because PUT modifies existing record, not creates new).
You are probably interested in some particular use case, like forwarding a text message. We could support it in the future. Please let us know what particular scenarios you need us to support in our API and we will consider them in our future design and implementation plan.
2 People are following this question.
