# Naming Breakout Rooms

**URL:** <https://devforum.zoom.us/t/naming-breakout-rooms/68618>\
**Category:** Zoom Apps\
**Created:** [May 6, 2022, 10:21pm UTC](https://devforum.zoom.us/t/naming-breakout-rooms/68618 "2022-05-06T22:21:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![om7](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/om7/32/36428_2.png) [@om7](https://devforum.zoom.us/u/om7)\
**Post date:** [May 6, 2022, 10:21pm UTC](https://devforum.zoom.us/t/naming-breakout-rooms/68618/1 "2022-05-06T22:21:21Z")

</div>

Hey @evgeny.balashov & Zoom team,

We’re trying to create an app with fully customized breakout rooms, and an integral part of the experience is adding names.

The `renameBreakoutRoom()` method works effectively, but it currently only applies to one breakout room. Often in our app we’ll create **50 breakout rooms** - this results in 50 subsequent `renameBreakoutRoom()` API requests to update each room name.

* * *

We’re wondering if you’d considered the following:

1. accepting other room configuration (such as names) or even a breakout room list in `createBreakoutRooms()` or `configureBreakoutRooms()`

2. a `renameBreakoutRooms()` that accepts a breakout room list, or an array of breakout room IDs with corresponding names

* * *

This question of design relates a lot to [my other query regarding assigning participants to breakout rooms](https://devforum.zoom.us/t/issues-with-assign-participant-to-breakout-room/68616).

For example, If the `createBreakoutRoom()` method could accept a breakout room list (or similar consistent data structure) then we could easily create and configure the rooms including participant assignment, room names and more with only a handful of API calls 🎉

Any thoughts? Has anybody else approached this in a different manner?

Thanks!

---

<div class="post-metadata">

**Author:** ![evgeny.balashov](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/evgeny.balashov/32/35990_2.png) [@evgeny.balashov](https://devforum.zoom.us/u/evgeny.balashov)\
**Post date:** [June 14, 2022, 2:01am UTC](https://devforum.zoom.us/t/naming-breakout-rooms/68618/2 "2022-06-14T02:01:55Z")

</div>

@om7 Thanks for the suggestions, we will put it on the roadmap, but it will take a few releases to complete

---

<div class="post-metadata">

**Author:** ![om7](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/om7/32/36428_2.png) [@om7](https://devforum.zoom.us/u/om7)\
**Post date:** [June 14, 2022, 2:21pm UTC](https://devforum.zoom.us/t/naming-breakout-rooms/68618/3 "2022-06-14T14:21:09Z")

</div>

Thanks @evgeny.balashov this one is much more of a nice-to-have 😄

We decided to implement the `renameBreakoutRoom` API in a loop over each Breakout Room, and it seems to work in Production, even or 50 rooms! 🥳

---

<div class="post-metadata">

**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\
**Post date:** [June 24, 2022, 11:43pm UTC](https://devforum.zoom.us/t/naming-breakout-rooms/68618/4 "2022-06-24T23:43:10Z")

</div>

Closed on June 24, 2022, 11:43pm UTC