Session Download Metadata API

更新日 29 May 2020
1 読む分

印刷する
共有
闇
光
PDF

The content is currently unavailable in Ja - 日本語. You are viewing the default English version.

記事の要約

この要約は役に立ちましたか?

ご意見ありがとうございます

API Specification:

The {PIN} part of the URL should be substituted with the 6-digit numeric code entered by the user

For production env:

GEThttps://api-v3.screenmeet.com/v3/support/{PIN}/meta

Sample responses:

Invalid:

HTTP STATUS CODE: 404

Sample Response Body:

{

"code": 404,"refcode": 101404,"description": "Session not found 123456"}

Valid:

HTTP STATUS CODE: 200

Sample Response Body:

{

"id": "fBjiPO","pin": 104066,"userDescription": "John Smith","status": "new","settings": {"recording": true},"expiresAt": "2019-03-15T22:53:36.000Z","OrganizationId": 26,"client_info": {"win_download_url": "https://downloads.screenmeet.com/windows/prod/v3/support?session=","mac_download_url": "https://downloads.screenmeet.com/mac/prod/v3/support?session=","ios_itunes_url": "itms-apps://itunes.apple.com/us/app/screenmeet-for-support/id1243134245?mt\\=8","android_package_id": "com.projector.screenmeet.support"}}

Constructing download URL/redirect:

Parse out the value body.client_info.win_download_url value from the body. Append the session pin to the URL.

Implementation Guidelines

Once you retrieve the download metadata for the desired session, you will need to detect the userAgent of the browser, then redirect them to the appropriate download for their system type.

この記事は役に立ちましたか?