App

Signatureapi integrations

Connect Signatureapi to any other app, or use it from your AI client over MCP. API for generating documents from templates and collecting legally binding electronic signatures.

Connects with an API keysignatureapi.com

15 actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

Build solutions, not workarounds.

What do you want to automate with Signatureapi?

Ask the assistant

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

Set it up in your client

Claude Code

Run this in the directory you want to work in.

claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai

Start Claude Code there, approve the server, and sign in in the browser page it opens.

Claude Code guide

Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

Setup guide

Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

Setup guide

Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

Setup guide

Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

Setup guide

Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

Setup guide

Popular

Signatureapi with the apps people pair it with most

Pair it

Connect Signatureapi with another app

What your agent can do with Signatureapi

Triggers and actions 15 actions

Action
Add ceremony
Creates a new signing ceremony for a recipient. Any previous active ceremony for that recipient is revoked. Returns the ceremony, including its URL when the recipient is authenticated by email code or by your own application.
Action
Add deliverable
Creates an additional deliverable (signed PDF package) from a completed envelope. The envelope must be completed.
Action
Add envelope
Creates an envelope with documents and recipients and starts the signing process.
Action
Add upload
Uploads a PDF, DOCX or PNG file to SignatureAPI and returns a URL you can use as a document source when creating an envelope. Uploads expire after 24 hours.
Action
Cancel envelope
Cancel an in-progress envelope so remaining recipients can no longer sign.
Action
Delete envelope
Delete an envelope.
Action
Get deliverable
Retrieves a deliverable by its ID, including its status and, once generated, a download link for the signed PDF.
Action
Get envelope
Retrieve a single envelope by id.
Action
Get recipient
Retrieves a recipient's details, including status, ceremony information and completion timestamp.
Action
Get upload
Fetches an uploaded file's record by ID: its format, size, hash and expiry. An error occurs if the upload is not found.
Action
List deliverables
Returns the deliverables (signed PDFs with audit log) of an envelope, earliest first.
Action
List envelopes
Lists envelopes in the account, most recent first, optionally filtered by status or topic.
Action
Resend request
Resends the signing request to a recipient who has not yet completed their ceremony, e.g. as a reminder or after a lost or soft-bounced email.
Action
Update envelope
Update mutable fields (e.g. title, metadata) of an existing envelope.
Action
Update recipient
Replaces a recipient who has not yet completed with a new person. The original recipient is marked replaced and a new recipient is created with the same type, key, routing position and places.

Reviews

What our customers say

Questions

Signatureapi, answered

Is there a Signatureapi MCP server?

APIANT's MCP server at https://mcp.apiant.ai works with Signatureapi. Add that address to any AI client that takes a remote MCP server and sign in once in your browser. Your client can then run Signatureapi actions on demand, or have APIANT build, test and run automations that use Signatureapi. Nothing to install.

What can your agent do in Signatureapi?

Any of Signatureapi's 15 actions, including Update envelope, Update recipient, Add ceremony and Add deliverable. Your agent maps the data both ways and tests every scenario before it ships.

Can I use Signatureapi directly from Claude, ChatGPT or Cursor?

Yes. Connect your AI client to APIANT once and it works with Signatureapi two ways. Ask it to do something in Signatureapi once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running on its own. A one-off action uses your plan's tasks the same way an automation step does.

Do I need to write code against the Signatureapi API?

No. APIANT connects to the Signatureapi API for you, with your Signatureapi API key. Describe what you want in plain language and your agent builds it on the Signatureapi triggers and actions in the catalog. If you need an endpoint that is not there yet, your agent reads the Signatureapi API documentation and adds it.

Which apps can Signatureapi connect to?

Any app in the catalog; the list on this page pairs Signatureapi with each of them. If the other app is missing, point your agent at its API documentation and it builds the connector.

What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.