Guide
How to Send a Document for Signature
The simplest way to send a document for signature is a single API call.
Steps
- 1
Prepare your document as markdown text or PDF URL
- 2
Call the Signbee API with sender and recipient details
- 3
Recipient gets an email with a secure signing link
- 4
Both parties sign with animated handwriting signatures
- 5
Signed PDF with SHA-256 certificate delivered to both
Try it with curl
curl -X POST https://signb.ee/api/send \
-H "Content-Type: application/json" \
-d '{
"content": "# Your Document\n\nContent here...",
"senderName": "Your Name",
"senderEmail": "you@email.com",
"recipientName": "Recipient",
"recipientEmail": "recipient@email.com"
}'Legal validity
Electronic signatures are legally binding under the ESIGN Act (US), eIDAS Regulation (EU), and Electronic Communications Act (UK). Every Signbee document includes a SHA-256 tamper-proof certificate.
More details
Sending a document for signature should take seconds, not minutes. Most e-signature platforms require you to create an account, upload a document, drag-and-drop signature fields, and configure recipients through a UI. With the API approach, it's one HTTP POST.
Two document formats supported: 1. Markdown text: Write your document content as markdown. Signbee renders it as a professional PDF with headers, lists, and formatting. 2. PDF URL: Pass a URL to an existing PDF. Signbee adds the signing experience and certificate page.
What the API call includes: - content: Your document text (markdown) or pdfUrl - senderName and senderEmail - recipientName and recipientEmail - Optional: subject line, message, expiry date
What happens after sending: 1. Signbee generates the PDF (if markdown) or fetches it (if URL) 2. Recipient receives an email with a secure signing link 3. Recipient reviews, signs with animated handwriting 4. Sender receives signing notification 5. Both parties get the certified PDF with SHA-256 certificate
No field placement, no envelope management, no drag-and-drop UI. One endpoint, one call, legally binding.
Frequently asked questions
Can I send documents for signature via API without a UI?
Yes. The entire signing flow is API-driven. One POST request sends the document, generates the signing link, and notifies the recipient. No dashboard or UI interaction needed.
What document formats are supported?
Markdown text (rendered as PDF) and PDF URLs (fetched and used directly). Markdown is ideal for programmatically generated documents; PDF URLs work for pre-existing documents.
Related resources
Try Signbee — free, no credit card.