Forwarding a message to another extension

  • 1
  • Question
  • Updated 3 years ago
  • Answered
  • (Edited)
A developer writes:

 

I’ve 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.
Photo of TT

TT, Alum

  • 412 Points 250 badge 2x thumb

Posted 3 years ago

  • 1
Photo of Anton Nikitin

Anton Nikitin, Official Rep

  • 2,904 Points 2k badge 2x thumb

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.