Schedule_for vs userid in path parameter

Description
When creating a meeting, Is there any difference between setting “schedule_for” and putting the username in the path parameter (/users/{userId}/meetings)?

Error
none

Which App Type (OAuth / Chatbot / JWT / Webhook)?
JWT

Which Endpoint/s?
Create Meeting
/users/{userId}/meetings

How To Reproduce (If applicable)

Screenshots (If applicable)
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Hi @mikehan yes, this is a different action. If you have permission to schedule a meeting for the user (as a JWT app), you should use the userID in the path of the request.

When using the “schedule_for” option, the userID in the path of the request would need to have scheduling privilege assigned to them for each user they are scheduling for.