Signclad
Start free

Connected to what you already use.

Two lists, kept honest. Available means you can use it today. Planned means it is on the roadmap and not built yet — no “coming soon” logo walls, no integration listed because a competitor lists it.

Everything below marked planned does not exist yet, and developer preview means it runs but is not finished. Until a connector ships, the API, webhooks, and plain HTTP calls cover the same ground. If one of these is what would make Signclad usable for you, tell us and it moves up the list.
Integration Status What it does
REST API Available The whole product, under /api/v1. Versioned by date, with idempotency on every write.
Webhooks Available Per-workspace endpoints with body signatures, health states, a delivery log, and replay.
MCP server Available Hosted, with OAuth sign-in. Connects Claude, Cursor, and other MCP clients to a workspace with nothing to install.
Embedded signing and builders Available Signing, the document builder, and the template builder inside your own product, with your branding.
Zapier Developer preview Instant triggers for sent, viewed, signed, declined, expired, completed, and template created; actions to send, send from a template, remind, cancel, and get a template link. Not listed in Zapier’s directory yet.
Google Drive Available One-way backup: every completed document is filed into a folder in your own Drive as it finishes, with its audit trail. Signclad only ever writes, never reads or deletes, and nothing syncs back. Sending from a Drive file is still planned.
Dropbox Available The same one-way backup, into a folder Dropbox creates for Signclad, which is all it can see. Sending from a Dropbox file is still planned.
OneDrive Planned The same one-way backup as Google Drive and Dropbox, for Microsoft 365 and personal accounts.
QuickBooks Online Planned Send an estimate or a contract for signature and write the signed result back against the customer record.
Xero Planned The same shape as QuickBooks Online: send for signature, attach the sealed PDF to the contact.
Close Planned Send from an opportunity and log status changes back onto the lead as activities.

Building it yourself

Every connector above is written against the same public API you have. There is no private endpoint that only our integrations can call.

  • Send from your own system

    One POST with a presigned file URL and a recipient. Add an idempotency key and a retry after a timeout is safe.

  • React to what happens

    Subscribe to the events you care about, verify the body signature, dedupe on the event id, and replay anything you missed.

  • Put it in your product

    The builder and the signing view in an iframe, branded as yours, with your allowed domains.

Send your first document today.

The free plan covers three documents a month, with the same sealed PDFs and audit trails as every paid plan. No card required.

Start free Read the API reference