Create a DocuSign developer account and register an integration key at developers.docusign.com; production access to Rooms for Real Estate requires a paid DocuSign account
Authenticate using OAuth 2.0 JWT Grant for server-to-server integrations or Authorization Code Grant for user-facing apps; obtain an access token scoped to the rooms API
Create a new room by calling POST /v2/accounts/{accountId}/rooms with a name, role assignment, and field data payload representing transaction details
Add participants to the room using POST /v2/accounts/{accountId}/rooms/{roomId}/users with their role (agent, buyer, seller, title, etc.) and email address
Attach documents and forms by calling POST /v2/accounts/{accountId}/rooms/{roomId}/documents; documents can then be sent for eSignature via the DocuSign eSignature API within the room context
Subscribe to room webhooks (Connect) to receive notifications when room status changes, documents are signed, or tasks are completed
Known gotchas
DocuSign Rooms and DocuSign eSignature are separate API surfaces with separate authentication scopes; you need both if you want to both manage the transaction room and send envelopes for signature
Room field data (transaction details form) is schema-driven and fields vary by configured form template — inspect the available fields via GET /v2/accounts/{accountId}/room_templates before writing to them
Production Rooms access requires a DocuSign Rooms for Real Estate subscription; the developer sandbox has functional differences from production, particularly around form library availability
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp