> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# Rooms API | Developer Deep Dive

#### Rooms API | Developer Deep Dive

Real estate transactions often require agents to complete a laundry list of tasks, including downloading forms, printing, scanning, and emailing documents back-and-forth to multiple parties. With Rooms for Real Estate, realtors can rest assured knowing that their entire transaction is securely handled and organized end-to-end. In this episode, we’re sitting down with Mike Friel, senior software engineer, to talk about the Rooms API, which enables developers to dynamically create, push data to, and pull data from these secure, digital transaction workspaces. In the DocuSign Developer Deep Dive Discussions series, our developer evangelism team sits down with the engineers and experts who build our APIs and tools, offering insights and demonstrations on best practices to speed up your development.