When I try to delete a user through the API, I get an error like:
Please remove it from schedules: [My Test Schedule]'
how can I delete a user from the schedule through the API?
p. s. I am trying to automate the issuance of access, the user may have many schedules
Earlier, he also wrote that you need to remove a user from the team, but it was not difficult here, I easily found a way in the documentation https://docs.opsgenie.com/docs/team-member-api#remove-team-member
Hi @Mikhail ,
You can find the user's schedules by first running a GET to list all users, and grab the user's ID that needs to be removed from any schedules: https://docs.opsgenie.com/docs/user-api#list-user
Then list the user's schedules using this API call: https://docs.opsgenie.com/docs/user-api#list-user-schedules
From here, you'd have to run a GET on the schedules to show what rotation(s) the user is a participant in: https://docs.opsgenie.com/docs/schedule-api#get-schedule
Following that - run a GET on that schedule's rotation to grab the body of the request: https://docs.opsgenie.com/docs/schedule-rotation-api#get-schedule-rotation
And finally, run a PATCH using the body from the previous request to update the rotation / schedule - and remove the user as a participant: https://docs.opsgenie.com/docs/schedule-rotation-api#update-schedule-rotation-partial
NOTE - when a user is removed from a rotation, that rotation will be rebuilt with the remaining users from the Stars On date set on the rotation. This could adjust who is currently on-call in a schedule. So in the PATCH or a following one, you may also need to update the rotation's Starts On date to reflect who should be on-call.
Hope this helps! Let us know if you have any questions or issues.
While Nick's answer is technically correct, I would suggest to first by first starting to remove the user from all teams.
For some reason, when a user is a member of a team, it also says they are a member of the schedule and escalation policy of that team as well, even if they aren't physically in a rotation or escalation policy.
The endpoints needed for this are:
After removing the Team membership, then I would proceed as Nick suggested.
Back in April of last year one of the major product announcements from Opsgenie was the launch of the Incident investigation view which created a deep connection between Bitbucket and Opsgenie, empow...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events