PATCH schedule_for (meeting owner) from one licensed Pro user to another

[roger.miller1 (Roger Miller)]

**API Endpoint(s) and/or Zoom API Event(s)
https://api.zoom.us/v2/meetings/89799078083 -
Attempting to PATCH a meeting owner from one user to another. Token works for other endpoints. Getting the following response error:
{“code”:3000,“message”:“You cannot schedule a meeting for valid user email.”}

Description
I’ve granted ALL of the scopes to the Zoom App for the Meeting, User and Admin scope sections. This didn’t help.
As outlined on this page: https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0061749#h_a9476921-e417-4d02-bf62-7bc96554f9a4, I’ve granted “Assign privilege to” all of the full licensed Zoom users in the Account and all are checked with “Can manage my private events”
Followed steps as outlined on: Transfer meetings from one user to another

Full Request Body:
{
“schedule_for”: “ydeconescu@workforceprofessionals.org”,
“settings”: {
“alternative_hosts”: “dsenthil@workforceprofessionals.org”,
“alternative_hosts_email_notification”: true
},
“type”: 2
}

Error?
response

Response Status

400

Response Headers

Response Headers Alt Svc

h3=“:443”; ma=86400

Response Headers Cache Control

no-cache, no-store, must-revalidate, no-transform

Response Headers Cf Cache Status

DYNAMIC

Response Headers Cf Ray

8e85f0348ef907d9-IAD

Response Headers Connection

close

Response Headers Content Length

98

Response Headers Content Type

application/json;charset=UTF-8

Response Headers Date

Tue, 26 Nov 2024 00:59:52 GMT

Response Headers Expires

Thu, 01 Jan 1970 00:00:00 GMT

Response Headers Nel

{“success_fraction”:0.01,“report_to”:“cf-nel”,“max_age”:604800}

Response Headers Pragma

no-cache

Response Headers Report To

{“endpoints”:[{“url”:“https://a.nel.cloudflare.com/report/v4?s=NT7zL%2B2ZNVBdU9SjKQfX8zT1qwzwHToQF%2F0NimsbYOBlNxF5kYhB2u0FtzpzIcY6QcIffUBkkT%2BF8jhH9VpPwrwube%2BWerQZuaqEUgPCdPs2ZOsIe2NWWqtvnA%2BG”}],“group”:“cf-nel”,“max_age”:604800}

Response Headers Server

cloudflare

Response Headers Set Cookie

zm_aid=; Max-Age=0; Expires=Thu, 01 Jan 1970 00:00:10 GMT; Domain=zoom.us; Path=/; Secure; HttpOnly, zm_haid=; Max-Age=0; Expires=Thu, 01 Jan 1970 00:00:10 GMT; Domain=zoom.us; Path=/; Secure; HttpOnly, zm_tmaid=; Max-Age=0; Expires=Thu, 01 Jan 1970 00:00:10 GMT; Domain=zoom.us; Path=/; Secure; HttpOnly, zm_htmaid=; Max-Age=0; Expires=Thu, 01 Jan 1970 00:00:10 GMT; Domain=zoom.us; Path=/; Secure; HttpOnly, cred=7BC8A954DAE32F085ACE095B192729C0; Path=/; Secure; HttpOnly, _zm_ctaid=; Max-Age=0; Expires=Thu, 01 Jan 1970 00:00:10 GMT; Domain=zoom.us; Path=/; Secure; HttpOnly, _zm_chtaid=; Max-Age=0; Expires=Thu, 01 Jan 1970 00:00:10 GMT; Domain=zoom.us; Path=/; Secure; HttpOnly, _zm_mtk_guid=0cdbe2e44a784189b8153322d32d27ab; Max-Age=63072000; Expires=Thu, 26 Nov 2026 00:59:52 GMT; Domain=zoom.us; Path=/; Secure, _zm_ctaid=; Max-Age=0; Expires=Thu, 01 Jan 1970 00:00:10 GMT; Domain=zoom.us; Path=/; Secure; HttpOnly, _zm_chtaid=; Max-Age=0; Expires=Thu, 01 Jan 1970 00:00:10 GMT; Domain=zoom.us; Path=/; Secure; HttpOnly, _zm_mtk_guid=d5776be181254ae4bfcb9b338be5b5d2; Max-Age=63072000; Expires=Thu, 26 Nov 2026 00:59:52 GMT; Domain=zoom.us; Path=/; Secure, __cf_bm=.lWs3.Y.9mcD8.Fp2PU6HjjbNNjp2Bz7RKs8mGDPpm8-1732582792-1.0.1.1-TPmBy9fcN26bJnp79HA5lMpIWRK_YfFezcNdTnd5.A8SK24GvSLtysORvn.SNqUYWu7kls4RvgN0ZlE6MioaVQ; path=/; expires=Tue, 26-Nov-24 01:29:52 GMT; domain=.zoom.us; HttpOnly; Secure; SameSite=None

Response Headers Vary

Origin, Access-Control-Request-Method, Access-Control-Request-Headers

Response Headers X Content Type Options

nosniff

Response Headers X Ratelimit Category

Light

Response Headers X Zm Trackingid

v=2.0;clid=us02;rid=WEB_267bc7bc40c55d4cebe24a17999bb356

Response Headers X Zm Zoneid

VA

Response Body

{“code”:3000,“message”:“You cannot schedule a meeting for ydeconescu@workforceprofessionals.org.”}

data

Response Data Code

3000

Response Data Message

You cannot schedule a meeting for ydeconescu@workforceprofessionals.org.

[Fario_Consulting]

Hi Roger,

Could you check if the meeting was initially created with the appropriate “schedule_for” value using POST /users/me/meetings.
Also check that the API user is registered as an assistant for both the intended host and the current meeting host.

Cheers,
Harsh
Fario Consulting

[roger.miller1 (Roger Miller)]

Thanks for the feedback @Fario_Consulting! For others who might need a bit of clarification, because I didn’t realize that this was necessary, the comment above: “Also check that the API user is registered as an assistant for both the intended host and the current meeting host”, I needed to go to every user who was going to have the API integration update meetings to them **For all users who the Zoom integration will update Zoom meetings to their user instead of the Zoom integration user, they need to grant access to the Zoom integration user to manage their meetings.

Go to Zoom>Users>Select a user>Settings>Meeting. Scroll all the way down to the bottom of the page and in the Schedule Privilege section, click on “Edit” next to “Assign scheduling privileges to” and add the Zoom integration user and all other users.