Register your application at info.dotloop.com/developers to obtain a client ID and client secret; API access requires the Enterprise plan
Implement the OAuth 2.0 authorization code flow to obtain a user access token (expires every 12 hours) and a refresh token for long-lived sessions
Create a transaction loop by calling POST /v2/loop with the required transaction type, name, and status fields; optionally populate participants and contacts in the same call using the Loop-It facade
Upload documents to a loop by calling POST /v2/loop/{loopId}/loopFolder/{folderId}/document with the file payload; documents can then be sent for e-signature
List all loops for a profile using GET /v2/loop with optional filters for status, transaction type, and modification date for incremental syncing
Subscribe to webhooks via POST /v2/webhook to receive real-time notifications when loop status, documents, or participant activity changes
Known gotchas
Access tokens expire after approximately 12 hours and must be refreshed using the refresh token; handle token expiry proactively rather than relying on 401 responses
Dotloop's API is user-scoped, not account-scoped — each API call acts on behalf of a specific Dotloop user and requires that user's access token, which complicates background service integrations
The Enterprise plan is required for API access; confirm with the account holder that the correct plan is active before beginning integration
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