meetings.getDialString
GET
https://relay.bluejeans.com/api/meetings/:id/dialstrings/:endpointid
For an existing scheduled meeting and provisioned endpoint, return a one-string dial string that can be used to join the endpoint into the meeting.
GET /api/meetings/539837779bab9338fa9a6a3e/dialstrings/4fb329c03a8ce62480d87e24 HTTP/1.1
HTTP/1.1 200 OK
Content-Type: application/json
"10990@bjn.vc"
inputs
id
The internal primary key of the scheduled meeting. This is not the "meeting ID" or "numeric meeting ID"
that you commonly see for Blue Jeans meetings, eg.
String
PATH
yes
10990. Instead, this is an autogenerated value that is created when the scheduled meeting
is synchronized from a calendar server to Relay. It comes from the id field of a Meeting object.539837779bab9338fa9a6a3e
endpointid
The ID of the endpoint that is provisioned in Relay. It comes from the
String
PATH
yes
id field of an Endpoint object.4fb329c03a8ce62480d87e24
outputs
A JSON string containing a one-string dial string. Looks like
application/json
String
"10990@bjn.vc". The quotation marks are part of the response body because the
body (like most other Relay API response bodies) is JSON-encoded, not plaintext.
If the meeting object does not have a Meeting ID (which typically means a room has been reserved without an associated video meeting), then the response
dial string will be for the IVR, not a one-string dial string.
If either of the given parameters do not belong to corresponding entities in the currently-authorized enterprise, then the response will be a 404 NotFound error.