Add legally binding e-signatures to a Python app in four steps with the GetSigned REST API: get a token, create an envelope, send the signing link, and handle the completion webhook. Uses requests and Flask — no SDK required.
Exchange your OAuth2 client credentials for a short-lived access token using the requests library.
Upload the PDF and declare signers and fields with a multipart 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 seals the document and POSTs envelope.completed to your endpoint. Verify the HMAC-SHA256 signature before trusting the payload.
Use the GetSigned REST API with the requests library: POST your client credentials to /oauth/token for a bearer token, create an envelope by POSTing a PDF with signers and fields as a multipart request, send it to generate signing links, then handle the envelope.completed webhook (for example in Flask) to fetch the sealed PDF. No SDK is required.
No. GetSigned is a plain REST API, so the standard requests library is enough for the full integration, and any web framework (Flask, FastAPI, Django) can receive the completion webhook.
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 Python integration.
Other stacks: Node.js guide · Language-agnostic guide