E-Signature API for HR: Automate Offer Letters, NDAs, and Employee Onboarding

An e-signature API for HR is a REST endpoint that programmatically sends employment documents — offer letters, non-disclosure agreements, I-9 forms, and benefits enrollment paperwork — for legally binding electronic signature. Unlike consumer e-signature tools that require manual uploads and template builders, an API integration connects directly to your HRIS (Human Resource Information System), ATS (Applicant Tracking System), or custom onboarding platform.

According to the Society for Human Resource Management (SHRM), the average cost-per-hire in 2025 was $4,700, with administrative paperwork accounting for 20-30% of that cost. Automating document signing eliminates the largest single bottleneck in the onboarding process.

The HR Onboarding Document Stack

A typical new hire signs between 5 and 8 documents before their first day. Here's what the document stack looks like for most companies:

Every one of these documents can be generated as markdown and sent for electronic signature via API. See our document templates for ready-to-use NDA and offer letter formats.

Manual vs API-Based Onboarding

How It Works: Sending an Offer Letter via API

When your ATS marks a candidate as "offer approved," your backend generates the offer letter from the candidate's data and sends it for signature with a single API call:

// When ATS triggers "offer_approved"
const res = await fetch("https://signb.ee/api/v1/send", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "Authorization": "Bearer YOUR_API_KEY",
  },
  body: JSON.stringify({
    markdown: `# Offer of Employment

**Company:** Acme Corp
**Position:** Senior Engineer
**Start date:** May 1, 2026
**Salary:** $145,000/year

This offer expires in 5 business days.

By signing, you accept the terms above.`,
    recipient_name: candidate.name,
    recipient_email: candidate.email,
    expires_in_days: 5,
  }),
});

const { document_id, status } = await res.json();
// status: "pending_recipient" — candidate gets email

The candidate receives an email with a signing link. Both parties get a SHA-256 certified PDF when signing is complete. No SDK, no client library — just fetch. See the full API documentation for all endpoints.

Tracking Document Status

After sending, poll the document status to update your HRIS:

const doc = await fetch(
  `https://signb.ee/api/v1/documents/${document_id}`,
  { headers: { "Authorization": "Bearer YOUR_API_KEY" } }
).then(r => r.json());

// doc.status: "pending_recipient" | "signed" | "expired"
if (doc.status === "signed") {
  // Update HRIS: mark onboarding step complete
  // doc.signed_pdf_url → store in employee file
}

The Business Case: HR Signing by the Numbers

According to Aberdeen Group research, companies with automated onboarding see a 17% higher offer acceptance rate and 54% greater new-hire productivity compared to those with manual processes. The speed of signing directly impacts whether a candidate accepts or takes a competing offer.

Legal Validity of Electronic Signatures in HR

Electronic signatures on employment documents are legally binding under three major frameworks:

• ESIGN Act (United States) — Covers all employment contracts, offer letters, and NDAs. I-9 forms have specific DHS requirements for electronic signatures but are permitted.
• eIDAS Regulation (European Union) — Simple electronic signatures are sufficient for standard employment contracts. Some member states require Qualified Electronic Signatures (QES) for specific labor law documents.
• Electronic Communications Act 2000 (United Kingdom) — Employment documents are fully valid with electronic signatures, with the exception of certain deeds requiring wet signatures.

For a deeper dive, see our guide: E-Signatures and the Law: eIDAS, ESIGN, and the ECA.

Integration Patterns for HRIS and ATS Platforms

The most common integration pattern is an event-driven webhook from your ATS or HRIS:

1. ATS triggers "offer approved" — your webhook handler receives the candidate data
2. Generate document — your backend creates the offer letter/NDA from a template with candidate-specific variables
3. Call Signbee API — POST /api/v1/send with the markdown and recipient details
4. Candidate signs — they click the link in their email, sign in-browser
5. Status callback — poll GET /api/v1/documents/{id} to detect completion
6. Update HRIS — mark onboarding step complete, store the signed PDF URL

This pattern works with any ATS or HRIS that supports webhooks or event triggers — including BambooHR, Workday, Lever, Greenhouse, and custom-built systems. No Signbee SDK is required. See our 20+ framework integration guides.

AI Agents in HR: Autonomous Document Signing

HR is one of the first departments where AI agents are handling document workflows autonomously. An AI recruiting agent can screen candidates, extend offers, and trigger the signing flow — all without human intervention for routine hires.

Signbee supports this through the Model Context Protocol (MCP), which lets AI agents like Claude, Cursor, and Windsurf call the send_document tool directly. See how to set up MCP signing in 2 minutes.

Frequently Asked Questions

Last updated: April 13, 2026 · Michael Beckett is the founder of Signbee and B2bee Ltd.