How docusign/sample-app-business-csharp works
Project type and purpose
• This is a full-stack Single Page Application (SPA) sample that demonstrates how to integrate DocuSign eSignature into a business workflow. The front end is an Angular client (under ClientApp) and the back end is a .NET 7.0 Web API project. It implements multiple use-cases (employment contract, T&Cs, customer profile update, custom quote) using DocuSign SDK, envelope builders, Connect notifications, and embedded signing.
File structure
• Top-level directories:
• ClientApp (Angular SPA)
• Controllers (Web API controllers, one per use-case)
• Domain (business logic, envelope builders and services)
• Infrastructure (DocuSign API provider, template builder, configuration, in-memory repo)
• Hubs (SignalR EventsHub for real-time updates)
• Templates (JSON and PDF templates for envelopes)
• appsettings*.json and private.key (configuration)
• Dockerfile and GitHub CI/CD pipeline
• The layering follows a clean architecture / onion pattern: Presentation (Controllers), Application/Domain (Services, Models), Infrastructure (external APIs), real-time hubs, and static templates.
README for additional insights
• Authentication via JWT grant or OAuth code grant
• Envelope composition for each use case using composite templates
• ‐level webhooks (event notifications)
• Embedded signing, remote signing, IDV/SMS authentication
• Local run via npm / dotnet or containerized via Docker