Using the webhook api v2/scheduler/schedules to create a schedule for another user does not work.
Scheduling privilege, same account and paid account criteria are satisfied and we are able to create the schedule for another user from Zoom web interface.
In the API request If we pass the userid in the v2/scheduler/schedules as request parameter we get 403 error with “message”: “no permission”
We’re using an “Account-level app” and “Server-To-Server OAuth”. This works for access token user though.
Hi @smdev , let me look into this. Can you please identify which scopes you have applied to the app and the permission level of the user making the request?
scope is “user:read:list_users:admin user:read:user:admin user:read:list_assistants:admin user:read:token:admin user:read:list_permissions:admin user:read:list_schedulers:admin user:read:email:admin user:read:settings:admin user:read:summary:admin user:read:list_collaboration_devices:admin user:read:presence_status:admin user:read:list_users:master user:read:user:master user:read:list_assistants:master user:read:token:master user:read:list_permissions:master user:read:list_schedulers:master user:read:settings:master user:read:summary:master user:read:presence_status:master meeting:read:list_meetings:admin meeting:read:meeting:admin meeting:read:list_registrants:admin meeting:read:registrant:admin meeting:read:list_registration_questions:admin meeting:read:livestream:admin meeting:read:invitation:admin meeting:read:list_templates:admin meeting:read:summary:admin meeting:read:list_past_instances:admin meeting:read:list_past_participants:admin meeting:read:participant:admin meeting:read:participant_feedback:admin meeting:read:participant_callout:admin meeting:read:alert:admin meeting:read:participant_sharing:admin meeting:read:device:admin meeting:read:risk_alert:admin meeting:read:chat_message:admin group:read:list_groups:admin group:read:group:admin group:read:administrator:admin group:read:lock_settings:admin group:read:list_members:admin group:read:settings:admin group:read:registration_settings:admin group:read:member:admin marketplace:write:app_request:admin marketplace:update:app_request:admin marketplace:read:app_request:admin marketplace:read:list_user_app_requests:admin marketplace:read:list_user_entitlements:admin marketplace:read:app:admin marketplace:read:list_webhook_logs:admin marketplace:read:list_apps:admin marketplace:write:app:master contact:read:list_contacts:admin scheduler:write:insert_schedule:admin scheduler:read:get_schedule:admin scheduler:read:list_schedule:admin scheduler:write:availability:admin scheduler:read:availability:admin scheduler:read:list_availability:admin scheduler:read:scheduled_event:admin scheduler:read:list_scheduled_events:admin scheduler:write:single_use_link:admin scheduler:read:user:admin calendar:read:event:admin calendar:read:color:admin calendar:read:acl:admin calendar:read:list_events:admin calendar:read:list_acl:admin calendar:read:instance_event:admin calendar:read:calendar:admin billing:read:user_entitlement:admin role:read:role:admin role:read:list_roles:admin role:read:list_members:admin role:read:role:master role:read:list_roles:master role:read:list_members:master”
The request is being made by the account owner
Hi @smdev ,
I’m going to private message you for the following info:
- dev email
- client id for app
- API response screenshot
- zm-tracking-id from API response header
- user email for both users (the one you cannot schedule for and the one you can schedule for)
- screenshot proof that you were able to schedule meeting for user via portal
Hi @smdev , just responded to you in the message again. Thank you for your patience and please be aware we have a high volume of developers we help through the forum. For SLA support, please consider a Support plan. You can see about the difference between the forum and support here: Zoom Developer Docs