Solved: Can GetjoinurlMeeting(XML API) appropriate for attendee account ?

OHua · ‎04-07-2022

Can GetjoinurlMeeting(XML API) appropriate for attendee account which is mentioned in Webex Help Center Article(https://help.webex.com/en-us/article/9dmqgv/Edit-Service-Licenses-in-Control-Hub-for-Individual-Users) ?

When attendee enter the link in browser, I need attendee account join meeting automatically login in background instead login by himself

And use attendee account information to join the meeting without typing by himself

Or another approach different from GetjoinurlMeeting(XML API) is OK, thanks for any advice

Rudrakshi · ‎04-19-2022

Please find below an example of the Request body that would generate an attendee specific join link where the user will not be prompted to enter any info an will be joined directly into the meeting:

<body>
  <bodyContent xsi:type="java:com.webex.service.binding.meeting.GetjoinurlMeeting">
    <meetingKey>1234567890</meetingKey>
    <attendeeName>Example User</attendeeName>
    <attendeeEmail>user@example.com</attendeeEmail>
    <meetingPW>password</meetingPW>
  </bodyContent>
</body>

The URL returned in the API response have an MTID string (MTID=m7c29598f********e139215") that has all of this information encoded so the attendee will be joined directly into the session without having to enter anything.

The documentation for the XML API seems to be not updated as per the latest format of the XML request and response. Our team has requested the documentation team to update the GetjoinurlMeeting description (https://developer.cisco.com/docs/webex-xml-api-reference-guide/#!getjoinurlmeeting/getjoinurlmeeting).

Best regards,
Rudrakshi Srivastava

View solution in original post

Rudrakshi · ‎04-19-2022

Please find below an example of the Request body that would generate an attendee specific join link where the user will not be prompted to enter any info an will be joined directly into the meeting:

<body>
  <bodyContent xsi:type="java:com.webex.service.binding.meeting.GetjoinurlMeeting">
    <meetingKey>1234567890</meetingKey>
    <attendeeName>Example User</attendeeName>
    <attendeeEmail>user@example.com</attendeeEmail>
    <meetingPW>password</meetingPW>
  </bodyContent>
</body>

The URL returned in the API response have an MTID string (MTID=m7c29598f********e139215") that has all of this information encoded so the attendee will be joined directly into the session without having to enter anything.

The documentation for the XML API seems to be not updated as per the latest format of the XML request and response. Our team has requested the documentation team to update the GetjoinurlMeeting description (https://developer.cisco.com/docs/webex-xml-api-reference-guide/#!getjoinurlmeeting/getjoinurlmeeting).

Best regards,
Rudrakshi Srivastava

sandiban · ‎04-07-2022

Hi @OHua

Thanks for sharing your queries here in Community portal directly.

Yes, using the GetjoinurlMeeting endpoint from XML Webex API, users can directly join the meeting. There should not be any problem regarding that.

Just a few additional pointers on using this API -

Host must need to start the meeting to get his/her attendees joined to the meeting
There will be a one-time use meeting URL generated with this API. Once the meeting is over, the auto-generated URL would be expired
Host needs to start the meeting first, otherwise the attendees won't be able to join the meeting
An expired one-time meeting URL won't work in future

Please let us know for any further assistance on this.
Thanks!
Sandip

OHua · ‎04-19-2022

Hi, @sandiban

still struggling

I have two host account A, B

first, I use user A to create a meeting on <siteId>.webex.com by chrome browser

and the meeting is starting at chrome browser

case 1:

<securityContext>
      <webExID><user_A_email></webExID>
      <webExAccessToken><user_A_oauth_token></webExAccessToken>
      <siteName><my_site_id></siteName>
</securityContext>

<bodyContent xsi:type="java:com.webex.service.binding.meeting.GetjoinurlMeeting">
      <sessionKey><meeting_sessionKey></sessionKey>
      <attendeeName>James Kirk</attendeeName>
</bodyContent>

case 2:

<securityContext>
      <webExID><user_B_email></webExID>
      <webExAccessToken><user_B_oauth_token></webExAccessToken>
      <siteName><my_site_id></siteName>
</securityContext>

<bodyContent xsi:type="java:com.webex.service.binding.meeting.GetjoinurlMeeting">
      <sessionKey><meeting_sessionKey></sessionKey>
      <attendeeName>James Kirk</attendeeName>
</bodyContent>

then, case1 and case2, response would be same like this:

"serv:bodyContent": {
        "@xsi:type": "meet:getjoinurlMeetingResponse",
        "@xmlns:xsi": "http://www.w3.org/2001/XMLSchema-instance",
        "meet:joinMeetingURL": "https://<my_site_id>.webex.com/<my_site_id>/m.php?MTID=m7c29598f********e139215",
        "meet:inviteMeetingURL": "https://<my_site_id>.webex.com/<my_site_id>/j.php?MTID=mcd363********ccba50e2ce3"
}

It's different from document example

It should has AN(attendeeName) in url parameter, isn't it?

Assume that GetjoinurlMeeting can return an url

attendee can enter this url in browser, then automatic login, join into meeting with his name and email
without typing by himself

any advice please