The signing API that does one thing well

Why Signbee exists

Every e-signature platform I evaluated wanted me to learn their template builder, configure signing fields through a web interface, and embed their SDK. I didn't need any of that. I had a document. I had a recipient. I needed a signature.

Signbee is the API I wish existed: one POST request with the document content and recipient details. That's it. The recipient gets an email, signs on any device, and both parties receive a certified PDF with a SHA-256 signing certificate.

Who builds Signbee

Michael Beckett

Founder & Developer

I'm a full-stack developer based in the UK, building developer tools and API-first SaaS products. Signbee is part of the B2bee Ltd portfolio — a collection of tools designed for the agentic web: AI agents, MCP servers, and autonomous workflows.

@mjcbeckett on X·hello@signb.ee

How it works

1. You call the API — POST to /api/v1/send with markdown or a PDF URL, plus recipient details.
2. Signbee generates the document — Markdown is converted to a clean PDF. Your PDF URL is fetched as-is.
3. Recipient signs — They receive an email with a signing link. They review and sign on any device.
4. Both parties get the certified PDF — Every signed document includes a SHA-256 signing certificate with timestamps, IP addresses, and both signatures.

Three ways to integrate

Legal validity

Electronic signatures created through Signbee are legally binding under the ESIGN Act (United States), eIDAS Regulation (European Union), and the Electronic Communications Act 2000 (United Kingdom). Every document includes a tamper-proof SHA-256 signing certificate that serves as the audit trail.

Pricing

Contact

Questions, partnerships, or feedback: hello@signb.ee