Sign

Legally binding e-signatures in your product, embedded or by email: how a request goes from PDF to a sealed document, and what's included.

coss.sign asks people to sign PDFs. They sign inside your app (an embedded signing page) or from a link coss.com emails them, and once everyone has signed you get a sealed PDF with a certificate of completion and a hash-chained audit trail. It uses the same API key, webhooks, logs and sandbox environments as everything else.

const { :  } = await ...({
  : "Services agreement",
  : [{ : "agreement.pdf", :  }],
  : [
    {
      : "Ada Lovelace",
      : "ada@example.com",
      : [{ : "signature", : "{{signature:signer_1}}" }],
    },
  ],
});

Signatures are simple electronic signatures under the US ESIGN Act and UETA and the EU's eIDAS: each signer agrees to sign electronically, signs with a deliberate act, and is identified by the link they opened or by your app; the audit trail records each step, and the completed PDF is sealed, so any later change shows.

How a request goes

  1. Create it with documents (uploaded or inline PDFs) and signers, each with their fields placed by position or by a text anchor in the PDF. It is sent at once, or a draft with send: false.
  2. Signers sign. delivery: "email" (the default) signers get an email with their link; "embedded" signers sign in your app, in an iframe you open for them (embedded signing). Before they see a document, each one agrees to sign electronically.
  3. It completes. When the last signer signs, coss.com seals the completed document and sends sign_request.completed. Download it with coss.sign.requests.signedDocument(id).

What's in it

Pricing

Each completed request is $0.50 per completed request, charged once when its sealed document exists, however many signers and documents it has. Declined, canceled and expired requests are free, and so are sandbox environments. The Free plan includes 5 signature requests completed requests a month: a live request counts when it's sent (a canceled one gives its place back), and past that sending fails with 402 usage_limit_exceeded until the next month or an upgrade. See Billing.

Tools

  • CLI: coss sign upload, create, send, list, get, remind, cancel, download, audit and templates.
  • MCP server: coding agents get upload_sign_document, create_sign_request, send_sign_request, get_sign_request, get_sign_audit_trail, create_sign_session, list_sign_templates and more.
  • Other languages: the API reference shows every operation in Python, Go, Ruby, PHP, Java and .NET.

Last updated