Dylan Thiam November 16, 2026 API Manager, API Portal, Collaboration, Developer Experience, Regulatory Sandbox, Sandbox Chat Rooms: built-in support & collaboration What it does Who it's for How it works Key benefits and use cases Try it! For: bank API teams, programme managers, developers Chat Rooms are built into the OBP Portal and API Manager. Developers ask questions where they already work, and the bank’s team answers from the API Manager. Because the chat runs on the same platform as the APIs, support does not depend on an external app, and anyone allowed on the API instance can use it. What it does Chat Rooms give a portal its own conversation layer: Rooms: Open rooms that every signed-in user can read and post in, and closed rooms joined with a key. Rooms are scoped to one bank or to the whole platform. Conversations: Threads, @mentions, emoji reactions, unread counters and editing your own messages. Support: Developers ask in the Portal, and the team replies from the API Manager. Control: Permissions per participant, a joining key you can refresh to cut off access, and archiving that keeps a room readable. Who it's for Bank and programme teams API and developer-relations teams who answer developer questions Hackathon and sandbox organisers who need channels for teams, mentors and judges Regulators and banks running working groups Developers Ask a question in the Portal without leaving it Open a shared room for community Q&A Build bots and integrations on the Chat API How it works Create a room. Choose open or closed, and bank or platform scope. The creator gets every room permission. A room called general exists by default. Invite people. Share the room’s joining key, or add participants directly. Talk, then archive. Use threads, mentions and reactions. When a round or a project ends, archive the room. It can stay readable but takes no new messages. Developers can read and post through the Chat endpoints in the API Explorer. They get near-real-time updates by polling, or through an optional gRPC stream. Key benefits and use cases Chat Rooms give a platform its own conversations, whether that is developer support, hackathon channels, working groups or programme discussions. They run on your own OBP instance, under the same access rules as the APIs, so there is no external app to add. Key benefits Support inside the Portal, answered from the API Manager No extra tool to approve: access follows the same rules as the API instance Closed rooms for any group, with a key you can refresh Room permissions, plus OBP Roles to archive or delete rooms Deleted messages are kept as records, and archived rooms stay readable Example use cases Developer support for a bank’s API portal, next to the API Explorer and Opey A hackathon with rooms for teams, mentors and organisers Working groups for a regulator and banks around a new standard or sandbox Discussion spaces for a startup innovation programme Try it! Test it yourself! Open chat rooms, create a room, share its key and post a first message. You can also call the Chat endpoints from the API Explorer. Want to see it with your own portal? Contact us for a demo and tell us who your developers are.