10-23-2024 06:58 AM
We have a package that runs in Salesforce to do appointment scheduling. It integrates with the Webex API. One of our clients is getting an error we haven't seen before. I'm hoping someone can shed some insight...
The request is-- POST https://api.zoom.us/v2//meetings Content-Type:application/json Accept:application/json
{
"hostEmail":"redactedEmail@redactedCompany.com",
"enabledAutoRecordMeeting": false,
"allowAnyUserToBeCoHost": false,
"title": "Test Meeting",
"start": "2024-10-22T10:00:00",
"end": "2024-10-22T10:30:00",
"timezone": "America/Los_Angeles",
"sendEmail": "false"
}
The response is ...
400 Bad Request Transfer-Encoding:chunked X-Envoy-Upstream-Service-Time:2027 Server:istio-envoy X-Content-Type-Options:nosniff;nosniff Request_Site_Url:mrs-achm.webex.com:443 Pragma:no-cache Trackingid:ROUTERGW_3dbe6b01-2beb-4942-95cd-ba22991b3897;ROUTERGW_3dbe6b01-2beb-4942-95cd-ba22991b3897 Date:Mon, 21 Oct 2024 23:42:50 GMT Wbx3:1 X-Frame-Options:DENY Cache-Control:no-cache, no-store, max-age=0, must-revalidate Set-Cookie:trackingSessionID=5AA832D275B54F3FBC18772C3F9328E1; Path=/; Secure; HttpOnly Vary:origin,access-control-request-method,access-control-request-headers,accept-encoding Expires:0 Content-Type:application/json
{"message":"Session type not found by Session type ID","errors":[{"description":"Session type not found by Session type ID"}],"trackingId":"ROUTERGW_3dbe6b01-2beb-4942-95cd-ba22991b3897"}
02-16-2025 06:52 AM
@j.claes replied in your support ticket. The hostEmail part was missing from your request.
02-17-2025 03:14 PM
02-16-2025 01:30 AM
Hello all, I guess I have the same problem, but where do I find "Check if the default session type of the admin is assigned to that user under hostEmail" ??
If I create meetings with "personal access token" => everything works
If I change to access_token for service-app, I receive 400 bad request "Session type not found by Session type ID"
kind regards,
johan claes
10-24-2024 06:18 AM - edited 10-24-2024 06:18 AM
@KenKoellner That error can happen if the user you're trying to schedule on behalf of doesn't have the sessionType assigned to them that the admin is trying to schedule with. You are not specifying sessionType in this case, so it will try to use the default session type of the admin making the request. Check if the default session type of the admin is assigned to that user under hostEmail.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide