Altixia Sign bronze

Send a document for signature

Creates an envelope and sends it to its signers, who sign in the Altixia Sign web flow. Send one `data` Part {"skill": "send_for_signature", "title", "recipients": [{email, name, role?, signingOrder?, fields?: [{type?, document?, page, positionX, positionY, width, height}]}], "sendEmail"?, "meta"?: {subject, message, language, timezone, dateFormat, redirectUrl, signingOrder}} and name each PDF with a `url` Part (preferred: the service fetches it, so the bytes never pass through your context) or, as a last resort, a base64 `raw` Part. Or use a template instead of PDFs: "templateId" plus recipients, mapped onto the template's slots in signing order. Positions are percentages of the page; every SIGNER needs a SIGNATURE field. Replaying the same messageId returns the envelope already created instead of a second one. Answers with a task in TASK_STATE_WORKING (the task id is the envelope id) and one signing link per recipient.

• Send this contract to Marie and Paul for signature
• Have the client sign the engagement letter at https://example.com/letter.pdf
• Create a signature request from template 42 for marie@example.com

Follow a signature request

Reports where an envelope of your team stands: who signed, who has not yet, and who refused, with the reason. Send a `data` Part {"skill": "get_signing_status", "envelopeId"} — or set message.taskId to the envelope id — or call GetTask with the envelope id. A refusal is reported as TASK_STATE_REJECTED, distinct from a signature not yet given (TASK_STATE_WORKING).

• Has everyone signed the contract yet?
• Who still has to sign envelope_abc123?

Retrieve the signed document

Once every signer has signed and the document is sealed, returns links to the sealed PDFs and to the audit trail — never the bytes. Fetch them with an HTTP client and the same Authorization header; they are not public. Before sealing, answers with the current state instead. Send a `data` Part {"skill": "get_signed_document", "envelopeId"} or set message.taskId.

• Get me the signed contract and its audit trail
• Download the sealed documents of envelope_abc123

Altixia Sign MCP server

Streamable HTTP JSON-RPC endpoint, 27 tools over documents, envelopes, recipients, fields, attachments and folders. Takes an Altixia Sign API token (Authorization: Bearer api_…) relayed per request; the server holds no key. The five tools that touch local files are absent over HTTP by design.

Agent skill — sign a document in the browser

How a browser-driving agent signs a document from its signing link through the in-page WebMCP tool, and what the signing link authorises.