Guide
How to Sign a Document via API
The Signbee API lets you send documents for signature with a single HTTP POST.
Steps
- 1
Get an API key from signb.ee (free)
- 2
POST to /api/v1/send with document content
- 3
Include sender and recipient details in the JSON body
- 4
Signbee generates the PDF and sends a signing link
- 5
Both parties sign and receive the certified PDF
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
The Signbee API is designed for simplicity. While other e-signature APIs require multi-step envelope creation, field placement, and complex authentication flows, Signbee uses a single endpoint with a straightforward JSON body.
API endpoint: POST https://signb.ee/api/v1/send
Request body: - content: Your document in markdown format - pdfUrl: Or pass a URL to an existing PDF (alternative to content) - senderName, senderEmail: The sender's details - recipientName, recipientEmail: The recipient's details - subject: Optional email subject line - message: Optional personal message
Authentication: Bearer token in the Authorization header. Get your free API key from signb.ee.
Response: JSON with document_id and signing_url.
Comparison with other APIs: - DocuSign: OAuth 2.0 setup, envelope creation, document upload, field placement, recipient routing. Dozens of endpoints. - HelloSign: API key auth, but requires template management and field configuration. - Signbee: One endpoint, Bearer token auth, markdown or PDF input. That's it.
The simplicity isn't a limitation — it's a design choice. Most signing use cases don't need field placement, template management, or complex routing. They need: send document, get signature, deliver result.
Frequently asked questions
How many API endpoints does Signbee have?
One primary endpoint: POST /api/v1/send. This handles document creation, PDF generation, email delivery, and signing link creation in a single call. Additional endpoints exist for status checking and document listing.
What programming languages work with the API?
Any language that can make HTTP requests. The API is a standard REST endpoint — works with JavaScript, Python, Ruby, PHP, Go, Java, C#, Rust, or any other language with an HTTP client.
Related resources
Try Signbee — free, no credit card.