TypeScript · Integration

Add E-Signatures to Deno

Send documents for legally binding e-signature from your Deno application. One endpoint, no SDK required.

Quick start

  1. Get an API key from signb.ee (free, no credit card)
  2. Set SIGNBEE_API_KEY in your environment
  3. Add the code below to your app

Deno example

TypeScript
Deno.serve(async (req) => {
  if (req.method !== "POST") return new Response("Method not allowed", { status: 405 });

  const body = await req.json();
  const res = await fetch("https://signb.ee/api/send", {
    method: "POST",
    headers: {
      Authorization: `Bearer ${Deno.env.get("SIGNBEE_API_KEY")}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify(body),
  });

  return new Response(await res.text(), {
    headers: { "Content-Type": "application/json" },
  });
});

What happens

  1. Your app sends markdown or a PDF URL to Signbee
  2. Signbee generates a PDF (if markdown) and emails the recipient a signing link
  3. Recipient signs — both parties receive the signed PDF with SHA-256 certificate

Also works with AI agents

Install the MCP server to let Claude, Cursor, or Windsurf send documents directly:

npx -y signbee-mcp

Integration details

Deno is a secure JavaScript/TypeScript runtime built by the creator of Node.js. Adding e-signatures to Deno uses the built-in fetch API and Deno.serve — no external dependencies, no package.json, no node_modules.

Zero dependencies: Deno includes fetch, a built-in HTTP server, and TypeScript support natively. The entire e-signature integration is a single file with zero npm packages. This makes it ideal for lightweight services and edge deployments.

Security model: Deno requires explicit permissions for network access (--allow-net) and environment variables (--allow-env). Run with deno run --allow-net --allow-env server.ts for a secure, least-privilege deployment.

Deno Deploy: Deno Deploy is a globally distributed edge platform. Deploy your signing service to 35+ regions with zero configuration. Set SIGNBEE_API_KEY as an environment variable in the Deno Deploy dashboard.

Fresh framework: If you're using Deno's Fresh framework, add the API call in a route handler (routes/api/send.ts). Fresh's island architecture ensures the API key stays server-side.

JSR imports: Deno uses JSR (JavaScript Registry) and URL imports instead of npm. For utility libraries, import directly from jsr.io or deno.land/x without a package manager.

FAQs

How do I add e-signatures to Deno?

Get an API key from signb.ee (free, no credit card), set SIGNBEE_API_KEY in your environment, and add a single POST request to your Deno application. The recipient receives a signing link by email, signs on any device, and both parties get a SHA-256 certified PDF.

Does Signbee work with Deno?

Yes. Signbee is a REST API that works with any language or framework including Deno. Send a POST request with your document content, sender and recipient details, and Signbee handles the entire signing ceremony. No SDK required.

Do I need any packages for Deno integration?

No. Deno includes fetch, an HTTP server, and TypeScript support natively. The entire integration is a single file with zero dependencies. No package.json, no node_modules, no build step.

How does Deno's security model affect the integration?

Deno requires explicit permissions. Run with --allow-net (for API calls) and --allow-env (for the API key). This least-privilege model prevents accidental network access or environment variable exposure.

Can I deploy the Deno integration to the edge?

Yes. Deno Deploy distributes your signing service to 35+ global regions with zero configuration. Set SIGNBEE_API_KEY in the Deno Deploy dashboard. Your service runs close to your users worldwide.

Related resources

Try Signbee — free, no credit card.