Offer letters, NDAs, employment agreements, and policy acknowledgments — all legally e-signable, all automatable via the GetSigned API. Trigger signing from your ATS, bulk send to cohorts, and receive completion webhooks that drive onboarding.
ATS marks candidate as "offer extended" → fires a webhook to your backend.
Your backend calls POST /v1/envelopes with the offer-letter template ID, candidate name/email, and any pre-fill values (start date, role, compensation).
Call POST /v1/envelopes/{id}/send → candidate receives a signed, tokenized email link.
Candidate verifies identity via email OTP, reviews and signs the offer letter.
envelope.completed webhook fires → your backend advances the ATS stage to "offer accepted", triggers IT provisioning, schedules onboarding tasks.
Yes. Employment agreements, offer letters, NDAs, and most onboarding documents are standard contracts enforceable under the US ESIGN Act, UETA, and Canadian provincial electronic commerce acts. E-signatures for these documents are legally equivalent to handwritten signatures. I-9 employment eligibility verification has specific rules — the Department of Homeland Security permits electronic signatures for the employee section under certain conditions; verify current USCIS guidance for your situation.
Create a reusable template for the offer letter with signer roles (Candidate, HR Manager) and pre-placed fields. When a hire is made, your ATS or HRIS triggers a POST /v1/envelopes call with the template ID and the candidate's details. The candidate receives a signing link, completes signing with OTP verification, and the envelope.completed webhook fires — triggering provisioning, onboarding tasks, or CRM updates automatically. No manual steps required.
Create an NDA template once. For each new hire in the cohort, POST /v1/envelopes with the template_id and the hire's name and email, then POST /send. Fan out the requests concurrently (10–20 in parallel). Each hire gets their own independent envelope and signing link; their completed NDA is sealed separately and triggers its own webhook. Use a batch_id in the metadata field to correlate all envelopes in the cohort.
Every envelope generates a hash-chained audit trail: when the document was created (and its hash), when each signer viewed it, when OTP consent was recorded, when each field was signed, and when the document was sealed. An audit certificate page is appended to the sealed PDF listing all events with timestamps and IP addresses. This is the evidence chain that demonstrates the employee's informed consent — important for disputes about whether an agreement was actually signed.
Yes, via the REST API. Most HRIS (Workday, BambooHR, Gusto) and ATS (Greenhouse, Lever, Workable) support webhooks or Zapier-style automation. Trigger envelope creation from your HRIS when a hire reaches "offer extended" status, listen for envelope.completed to advance the hire to "offer accepted" and trigger onboarding. No native GetSigned integration is required — the REST API connects to any system that can make HTTP calls.
Informational only — not legal advice. Consult qualified employment counsel for jurisdiction-specific requirements.
Related: Bulk send guide · Template API · Webhook guide · E-signatures for SaaS