[doc-issue-14014] - Inserted documentation regarding new endpoint.

Author: GuiLeme

_data/insertDocument.yml

@@ -0,0 +1,4 @@
+- name: "meetingID"
+  required: true
+  type: "String"
+  description: "A meeting ID that can be used to identify this meeting by the 3rd-party application. <br><br> This must be unique to the server that you are calling: different active meetings can not have the same meeting ID. <br><br> If you supply a non-unique meeting ID (a meeting is already in progress with the same meeting ID), then if the other parameters in the create call are identical, the create call will succeed (but will receive a warning message in the response). The create call is idempotent: calling multiple times does not have any side effect.  This enables a 3rd-party applications to avoid checking if the meeting is running and always call create before joining each user.<br><br> Meeting IDs should only contain upper/lower ASCII letters, numbers, dashes, or underscores.  A good choice for the meeting ID is to generate a <a href=\"http://en.wikipedia.org/wiki/Globally_unique_identifier\">GUID</a> value as this all but guarantees that different meetings will not have the same meetingID."

_posts/2.5/2021-06-09-new.md

@@ -61,6 +61,14 @@ You can now pin a webcam so it always stays visible.  This is useful if one on o
 
 Private guest lobby message, display position in waiting line
 
+### Improvements to Endpoint API 
+
+#### New endpoint
+
+A new API endpoint was added: `/insertDocument`. Now, it is possible to send a batch of documents with all the common presentation parameters such as `current`, `downloadable` and `removable`. 
+
+All the presentations are sent via payload (the body of the request), whether by a link to download the file or by `base64` encoded file.
+
 ## Engagement
 
 ### Text message broadcasting to breakout rooms