Add legally binding e-signatures to a .NET app in four steps using HttpClient and MultipartFormDataContent: get a token, create an envelope, send the signing link, and handle the completion webhook in ASP.NET Core. No NuGet package required.
Exchange your OAuth2 client credentials for a short-lived access token using .NET's built-in HttpClient — no NuGet package needed.
Upload the PDF and declare signers and fields with MultipartFormDataContent — the .NET equivalent of a multipart/form-data request.
Sending generates a tokenized, single-use link per signer and emails it. Signers verify identity with email/SMS OTP.
When the last signer finishes, GetSigned POSTs envelope.completed to your ASP.NET Core endpoint. Verify the HMAC-SHA256 signature before trusting the payload.
Use .NET's built-in HttpClient and MultipartFormDataContent to call the GetSigned REST API: POST client credentials to /oauth/token for a bearer token, create an envelope by uploading a PDF with signers and fields as a multipart request, send it to generate signing links, then handle the envelope.completed webhook in ASP.NET Core (minimal API or controller). No NuGet package is required.
No. .NET's built-in MultipartFormDataContent (System.Net.Http) handles multipart/form-data natively. Add ByteArrayContent for the PDF file and StringContent for JSON-encoded signers and fields. No Refit, RestSharp, or other HTTP library is needed for a three-endpoint integration.
Register it in Program.cs: builder.Services.AddHttpClient<GetSignedService>() where GetSignedService is a typed client that encapsulates the token, envelope creation, and send calls. This gives you lifetime management, connection pooling, and easy testability via IHttpClientFactory. For a simple integration, a singleton HttpClient is also acceptable.
For minimal API endpoints (MapPost), CSRF protection is not applied by default. For controller endpoints, add [IgnoreAntiforgeryToken] to the action or controller. Always verify the HMAC-SHA256 signature in the X-GetSigned-Signature header as the authentication mechanism instead.
Yes. The free Starter plan includes full REST API access, PKCS#7 sealing, OTP verification, and webhooks, with 5 envelopes per month — enough to build and test a complete .NET integration.
Other stacks: Java · Node.js · Python · Go · Language-agnostic guide