Integration

SignatureAPI integration

SignatureAPI is a developer e-signature API. Create envelopes that send PDF or DOCX documents to signers, approvers and preparers (signing starts at once), track envelopes, recipients and their events, cancel or delete envelopes, replace or re-invite a recipient, create signing ceremonies for embedded or custom-authenticated signing, generate and fetch deliverables (the signed package), upload files and register sender addresses. Webhooks are configured in the SignatureAPI dashboard, not through the API. Authentication is an API key in the X-API-Key header: a key_test_ key creates free, non-binding test envelopes that email nobody; a key_live_ key sends real, billed envelopes. Default rate limit 10 requests per second per key.

Connect SignatureAPI How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in SignatureAPI.Built from the 23 SignatureAPI tools below, on the connection you add once.

What you can do with SignatureAPI

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Envelope, 6 operations

cancel_envelopeCancel envelopePOSTCancels an in_progress envelope at once and for good: recipients can no longer sign. An optional internal reason is kept in the audit trail.
create_envelopeCreate envelopePOSTCreates an envelope and starts signing at once: SignatureAPI emails the first recipients (live key, billed) unless a ceremony uses custom or email_code auth. Needs title, documents and recipients. Poll get_envelope for status.
delete_envelopeDelete envelopeDELETEPermanently deletes a canceled, completed or failed envelope (cancel an in_progress one first with cancel_envelope). Cannot be undone.
get_envelopeGet envelopeGETReturns an envelope with its status, documents, recipients (with status and ceremony), deliverable (download url once completed), sender and captured input values.
list_envelopesList envelopesGETLists envelopes, newest first, 20 per page at most; filter by status or topic. Pass the cursor from links.next to get the following page.
update_envelopeUpdate envelopePATCHChanges an envelope's internal label (never shown to recipients), whatever its status. The label is the only field this route can change.

Deliverable, 3 operations

create_deliverableCreate deliverablePOSTGenerates an extra deliverable from a completed envelope, for example only some documents or a password-protected copy. Poll get_deliverable until status is generated to get its url.
get_deliverableGet deliverableGETReturns a deliverable's status (pending, generated, failed) and, once generated, url: a download link valid 1 hour by default (call again for a fresh one).
list_envelope_deliverablesList envelope deliverablesGETLists an envelope's deliverables (the automatic one created at completion plus any made with create_deliverable), oldest first, 20 per page at most. Pass the cursor from links.next for more.

Event, 3 operations

list_envelope_eventsList envelope eventsGETLists an envelope's events (envelope, recipient and deliverable events), newest first, 20 per page at most; filter with type. Pass the cursor from links.next for more.
list_eventsList eventsGETLists every event in the account (envelope, recipient, deliverable and sender events), newest first, 20 per page at most; filter with type. Pass the cursor from links.next for more.
list_recipient_eventsList recipient eventsGETLists one recipient's events (sent, viewed, completed, bounced...), newest first, 20 per page at most. Pass the cursor from links.next for more.

Sender, 3 operations

create_senderCreate senderPOSTRegisters a sender email address; SignatureAPI emails it a confirmation link and the sender stays pending_verification until the owner clicks it (check with get_sender).
delete_senderDelete senderDELETEDeletes a sender; its address can no longer be used on new envelopes (envelopes already sent are unaffected).
get_senderGet senderGETReturns a sender's email and verification status (pending_verification, verified...).

Upload, 3 operations

create_uploadCreate uploadPOSTUploads a PDF, DOCX or PNG file (5 MB max) and returns its url to use as a document url in create_envelope. Temporary: deleted after 24 hours unless kept with store_upload.
get_uploadGet uploadGETReturns an upload's metadata: format, size, SHA-256, retention, key and expiry. The file content itself cannot be downloaded.
store_uploadStore uploadPOSTMakes a temporary upload permanent under a unique key so it no longer expires (for reusable templates).

Recipient, 2 operations

get_recipientGet recipientGETReturns one recipient with its type, status, current ceremony and completion time.
replace_recipientReplace recipientPOSTReplaces a recipient who cannot sign (hard bounce, wrong person) with a new name and email; the old one becomes replaced and the new recipient is invited.

Ceremony, 1 operation

create_recipient_ceremonyCreate recipient ceremonyPOSTCreates a new signing ceremony for a recipient (revoking the previous one), for example to embed signing in an iframe or authenticate in your own app. Returns the ceremony url for email_code or custom auth.

Invitation, 1 operation

resend_recipient_requestResend recipient requestPOSTEmails the signing invitation again to a recipient whose status is sent or soft_bounced on an in_progress envelope. can_resend_at says when the next resend is allowed.

Upload structure, 1 operation

get_upload_structureGet upload structureGETReturns the analyzed structure of an upload: pages and sizes, detected [[placeholders]] and, for DOCX templates, template fields, each with validation errors. Check it before create_envelope.

Use SignatureAPI from Claude Code, Cursor or Codex

Connect SignatureAPI in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its SignatureAPI operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect SignatureAPI

Create your workspace
Sign up free. Nothing to install.
Connect SignatureAPI once
Add your SignatureAPI connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.