Integration

SignRequest integration

SignRequest (a Box company) is an e-signature service. Create documents from a file URL, base64 content or a template, send them for signature (or create and send in one call), resend, forward or cancel SignRequests, read documents with their signed PDF and signing log links (valid five minutes), search documents, add attachments, read events and audit events, and manage templates, webhooks, teams and team members. Listing existing API tokens is not exposed. API access is on the Business plan (additional fees apply); a free sandbox team watermarks documents and is not charged. Authentication is a SignRequest API token from the team API settings page, sent as Authorization: Token <token>.

Connect SignRequest How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with SignRequest

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.

Signrequest, 6 operations

cancel_signrequestCancel signrequestPOSTCancels a SignRequest that is not fully signed or declined: signers who have not signed can no longer open or sign it. Cannot be undone.
create_signrequestCreate signrequestPOSTSends an existing document for signature: SignRequest emails every signer at once (unless is_being_prepared). Needs the document url from create_document and the signers.
forward_signrequestForward signrequestPOSTForwards a SignRequest from one signer to another email address; the new signer is invited and the optional reason is visible to everyone involved.
get_signrequestGet signrequestGETReturns a SignRequest with its signers (viewed, signed, declined, forwarded...) and settings.
list_signrequestsList signrequestsGETLists SignRequests with their signers and status flags page by page; filter by who or from_email.
quick_create_signrequestQuick create signrequestPOSTCreates a document and sends it for signature in one call: SignRequest emails every signer at once. Takes the document source (file URL, base64 or template) and the signers.

Webhook, 6 operations

create_webhookCreate webhookPOSTSubscribes a callback URL to one event type. Each POSTed event carries event_hash, an HMAC-SHA256 of event_time+event_type keyed with your API token, to check it came from SignRequest.
delete_webhookDelete webhookDELETEDeletes a webhook subscription; its URL stops receiving events.
get_webhookGet webhookGETReturns one webhook subscription.
list_webhooksList webhooksGETLists webhook subscriptions (event type, callback URL, team) page by page.
replace_webhookReplace webhookPUTReplaces a webhook subscription: event_type and callback_url are required and name or integration left out are cleared.
update_webhookUpdate webhookPATCHChanges some fields of a webhook subscription; a field left out keeps its value.

Document, 5 operations

create_documentCreate documentPOSTCreates a document from a file URL, base64 content or a template; nothing is sent. Send it with create_signrequest using the returned url. status starts at co (converting).
delete_documentDelete documentDELETEDeletes a document for its owner. Signers without a SignRequest account keep access for a grace period, then it is fully deleted. Cannot be undone.
get_documentGet documentGETReturns a document: status, signers and their progress, inputs, and the temporary links (valid five minutes) to the signed pdf and signing_log.pdf once signed.
list_documentsList documentsGETLists documents (with status, SignRequest, signers and signed PDF links) page by page; filter by status, external_id, sender or creator. count, next and page give the paging.
search_documentsSearch documentsGETFast (autocomplete) search of documents by text, name, signer email, status or ownership; returns light document rows page by page. Names match on words split by spaces, hyphens and underscores.

Team, 5 operations

create_teamCreate teamPOSTCreates a team; name and a globally unique subdomain are required.
delete_teamDelete teamDELETEDeletes a team (it is scheduled for deletion, see delete_after). Cannot be undone.
get_teamGet teamGETReturns one team with its members, branding and events callback URL.
list_teamsList teamsGETLists the teams the token's user belongs to, with subdomain, branding, callback URL and members.
update_teamUpdate teamPATCHChanges a team's name, phone, colour, events callback URL or attachment setting. name is required by SignRequest: send the current name back when not renaming. The subdomain cannot be changed.

Document attachment, 3 operations

create_document_attachmentCreate document attachmentPOSTAdds an attachment (a file signers can read, not sign) to a document before its SignRequest is created. Only for documents made from a file, not from a template.
get_document_attachmentGet document attachmentGETReturns one document attachment with its temporary file link (valid five minutes).
list_document_attachmentsList document attachmentsGETLists document attachments (files signers can read but do not sign) page by page; filter by document uuid or external id.

Team member, 3 operations

get_team_memberGet team memberGETReturns one team member with their user and roles.
invite_team_memberInvite team memberPOSTEmails an invitation to join a team, optionally as admin or owner.
list_team_membersList team membersGETLists the team's members with their user, admin/owner flags and activity, page by page.

Event, 2 operations

get_eventGet eventGETReturns one event with its document, signer (for signer events) and callback delivery details.
list_eventsList eventsGETLists document events (converted, sent, viewed, signed, declined, cancelled, expired...) with delivery status, page by page; filter by document, type or status.

Template, 2 operations

get_templateGet templateGETReturns one template with its placeholders (external ids usable as prefill_tags) and signer configuration.
list_templatesList templatesGETLists templates (made in the SignRequest interface) with their url, placeholders and signer configuration, page by page. Pass a template url to create_document.

Audit event, 1 operation

list_audit_eventsList audit eventsGETLists account audit events (logins, password resets, token and member changes...) page by page; filter by user email or IP, event type, status and date range (YYYY-MM-DD).

Reminder, 1 operation

resend_signrequest_emailResend signrequest emailPOSTEmails the SignRequest again, as a reminder, to every signer who received it and has not signed yet.

Use SignRequest from Claude Code, Cursor or Codex

Connect SignRequest in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its SignRequest 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 SignRequest

Create your workspace
Sign up free. Nothing to install.
Connect SignRequest once
Add your SignRequest 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.