Better: Add HTML Sending Guide for RingCX Messaging. RD-41088#273
Open
aymebou wants to merge 2 commits into
Open
Better: Add HTML Sending Guide for RingCX Messaging. RD-41088#273aymebou wants to merge 2 commits into
aymebou wants to merge 2 commits into
Conversation
aymebou
commented
Apr 11, 2026
| operationId: createContent | ||
| externalDocs: | ||
| description: Sending Rich Text Messages in RingCX Messaging | ||
| url: https://developers.ringcentral.com/engage/digital/guide/interactions/mobile-messaging/rich-text/ |
Contributor
Author
There was a problem hiding this comment.
Here's the preview on the swagger for that option for info, I'll also use it for the WA development guide when I'll create the page :
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hey !
Updating the documentation to showcase the API parameters for Rich text messages in /contents API route.
I did a guide to showcase the supported parameter types, & added the parameter to the swagger and the postman.
I added the guide in two sections, not sure if this is a good practice, but it shows that it's available in the two modes. let me know what you think.
Emplacement in the page :
And then the guide in screenshot, so that you can have a quick overview before diving in the code & eventual remarks. :