Unable to update meeting using Meetings API. Error: MET-109 [meeting_capacity] is not specified

  • 1
  • Problem
  • Updated 2 months ago
  • (Edited)
We're developing a 3rd party integration using the Meetings REST API. All good and well with the exception of updating existing meetings. Here's the API request:

PUT https://platform.devtest.ringcentral.com/restapi/v1.0/account/~/extension/~/meeting/[redacted meetingId] HTTP/1.1
Accept: application/json
Authorization: Bearer [redacted token]
Content-Type: application/json; charset=utf-8
Host: platform.devtest.ringcentral.com
Content-Length: 400
Expect: 100-continue
Accept-Encoding: gzip, deflate

{
"topic": "[update] Test ran on 12/10/2017 12:35 AM UTC",
"schedule": {
"startTime": "2018-01-10T01:30:00Z",
"durationInMinutes": 90,
"timeZone": {
"id": "1"
}
},
"meetingType": "Scheduled",
"allowJoinBeforeHost": false,
"startHostVideo": false,
"startParticipantsVideo": false,
"audioOptions": [
"Phone",
"ComputerAudio"
]
}

And the response:

HTTP/1.1 503 Service Unavailable
Server: nginx/1.10.2
Date: Sun, 10 Dec 2017 01:00:01 GMT
Content-Type: application/json;charset=UTF-8
Content-Length: 479
Connection: keep-alive
RCRequestId: 724c5008-dd45-11e7-97a3-005056bb26b9
RoutingKey: SJC11P01PAS02
Content-Language: en-US
X-Rate-Limit-Group: medium
X-Rate-Limit-Limit: 40
X-Rate-Limit-Remaining: 39
X-Rate-Limit-Window: 60
Retry-After: 40

{
"errorCode" : "MET-109",
"message" : "Cannot update meeting. Reason : [Response validation failure: [meeting_capacity] is not specified]",
"errors" : [ {
"errorCode" : "MET-109",
"message" : "Cannot update meeting. Reason : [Response validation failure: [meeting_capacity] is not specified]",
"reason" : "Response validation failure: [meeting_capacity] is not specified"
} ],
"reason" : "Response validation failure: [meeting_capacity] is not specified"
}
The problem is that there no documentation mentioning "meeting_capacity" parameter, when it should be sent and what values it needs to have.
Photo of Stefan

Stefan

  • 82 Points 75 badge 2x thumb

Posted 2 months ago

  • 1
Photo of Tyler Long

Tyler Long, Official Rep

  • 4,524 Points 4k badge 2x thumb
I've forwarded this question to the relevant team.
Photo of Phong Vu

Phong Vu, Devangelist

  • 1,520 Points 1k badge 2x thumb
Hi Stefan,

Is this your free developer account? What is your account's email address? If you don't want to post the email address here then send it over devsupport@ringcentral.com so we can check if your developer account is enabled to use meeting APIs.

+ Phong
Photo of Anton Nikitin

Anton Nikitin, Official Rep

  • 2,092 Points 2k badge 2x thumb
Stefan, can you recheck if the problem still exists?
(Edited)
Photo of Stefan

Stefan

  • 82 Points 75 badge 2x thumb
Hi Anton, we tried again on Dec 23 and same exact error response :(

HTTP/1.1 503 Service Unavailable
Server: nginx/1.10.2
Date: Sun, 24 Dec 2017 00:03:23 GMT
Content-Type: application/json;charset=UTF-8
Content-Length: 479
Connection: keep-alive
RCRequestId: da9d24b8-e83d-11e7-b7a9-005056bb26b9
RoutingKey: SJC11P01PAS02
Content-Language: en-US
X-Rate-Limit-Group: medium
X-Rate-Limit-Limit: 40
X-Rate-Limit-Remaining: 39
X-Rate-Limit-Window: 60
Retry-After: 40

{
  "errorCode" : "MET-109",
  "message" : "Cannot update meeting. Reason : [Response validation failure: [meeting_capacity] is not specified]",
  "errors" : [ {
    "errorCode" : "MET-109",
    "message" : "Cannot update meeting. Reason : [Response validation failure: [meeting_capacity] is not specified]",
    "reason" : "Response validation failure: [meeting_capacity] is not specified"
  } ],
  "reason" : "Response validation failure: [meeting_capacity] is not specified"
}
(Edited)