VAMOSIGNFree, on every plan

E-signature API and MCP: send from your own system

Short answer: create an API key in VAMOSIGN's Developers room and call ten actions over REST or MCP. Your system, a script or an AI assistant sends the request, the signers get their links by e-mail, and a webhook tells your system when a document is signed and sealed. No SDK: it is plain REST and the Model Context Protocol. Sending one document and checking its status work on every plan.

Step by step

For example: a case management system that sends an engagement letter when a case opens.

YouVAMOSIGNSigners and others
  1. 1
    Once · You

    You open Developers in VAMOSIGN and create an API key for the workspace.

  2. 2
    Once · You

    You add a webhook: an address in your system and the events you want, such as document.sealed.

  3. 3
    Case opens · Your system

    Your system calls send_for_signature with the document, a title and the signers. Over REST or as an MCP tool, it is the same action.

    POST https://app.vamosign.com/v1/send_for_signature
    Authorization: Bearer <your API key>
    Content-Type: application/json
    
    {
      "title": "Engagement letter",
      "document_base64": "…",
      "signers": [{"name": "Kari Nordmann", "email": "kari@example.com"}]
    }
    
  4. 4
    Same second · VAMOSIGN

    VAMOSIGN answers with the request's id and e-mails each signer their link.

  5. 5
    Later · The signers

    The signers sign in the browser, as with any request.

  6. 6
    Each signature · VAMOSIGN

    VAMOSIGN posts signature.completed to your webhook. The body is signed with HMAC-SHA256 in the X-Signer-Signature header, so your system can check it came from VAMOSIGN.

  7. 7
    When done · VAMOSIGN

    VAMOSIGN posts document.sealed. Your system calls check_status with the id to read who signed and when.

    GET https://app.vamosign.com/v1/check_status?id=…
    Authorization: Bearer <your API key>
    
    {
      "id": "…",
      "status": "completed",
      "sealed": true,
      "signers": [
        {"name": "Kari Nordmann", "email": "kari@example.com", "status": "signed", "signed_at": "2026-09-29T12:15:00+02:00"}
      ]
    }
    
  8. 8
    Any time · You

    The Developers room shows every webhook delivery, including the ones that failed.

Every argument

Every call needs two headers: your workspace API key as a bearer token, and Content-Type: application/json. The MCP tools take the same arguments, under the same names.

OpenAPI: https://app.vamosign.com/openapi.json

POST https://app.vamosign.com/v1/send_for_signature

Sends one document to one or more people. Give a template or a PDF.

titlestringrequired
The name of the document. The signers see it.
messagestring
A note to the signers. VAMOSIGN puts it in the invitation.
templatestring
The name or slug of a template. VAMOSIGN sends its current version.
document_base64string
The PDF, base64-encoded. Use this when you give no template.
filenamestring
The name of the file. If you leave it out, it is dokument.pdf.
order"parallel" | "sequential"
parallel: VAMOSIGN asks everyone at once. This is the default. sequential: VAMOSIGN asks them in the order you list them, and writes to each person when the one before has signed.
sign_bystring
The last day the link can be signed, as YYYY-MM-DD. After that day nobody can sign, and you can move the date. If you leave it out, the link stays open until everyone has signed.
expires_onstring
The date the agreement runs out, as YYYY-MM-DD.
expires_after_monthsinteger
The agreement runs out this many months after the last signature, from 1 to 120. Give this or expires_on, not both. Left out with a template, the template's own months stand.
send_nowtrue | false
Set it to false and VAMOSIGN keeps a draft, for a person to send from Documents. If you leave it out, VAMOSIGN sends at once.
questionsarray
What the signers must answer as they sign, one object each. Needs Team. A template's own questions are asked as well.
promptstringrequired
The question, as the signer reads it.
shape"short_text" | "long_text" | "one_of" | "several_of" | "yes_no" | "number" | "date"
How the signer answers. If you leave it out, it is short_text.
requiredtrue | false
Set it to false and the signer may leave the question empty. If you leave it out, the signer must answer before signing.
optionsarray
The choices, for one_of and several_of.
whostring
The e-mail address of the one signer who is asked. If you leave it out, VAMOSIGN asks everyone.
redact_after_weeksinteger
Weeks after the person signs that VAMOSIGN removes the answer: it empties it, seals the document again with the answer marked as removed, and tells you. 1 or more. If you leave it out, the answer stays with the document. On Team and above.
signersarrayrequired
The people who sign, one object each:
namestring
The person's name. If you leave it out, VAMOSIGN uses the part of their address before the @.
emailstringrequired
Where VAMOSIGN sends the link. VAMOSIGN skips a person without a valid address.
phonestring
A mobile number with its country code, such as +47. On Starter and above, VAMOSIGN also sends the link by SMS.
sign_method"simple" | "selfie"
simple: the person types their name. This is the default. selfie: the person takes a photograph of themselves on the signing page.
localestring
The language VAMOSIGN writes to this person in: en, nb, es. If you leave it out, VAMOSIGN uses your workspace's language.
companyobject
Left out, the person signs as a private person. Given, the company they sign for: name, org_number, country (two letters, such as NO) and, for a Norwegian company, check: signatur or prokura. With check, VAMOSIGN reads from Brreg who may sign for the company, and the certificate prints what Brreg said when the document was sealed.

You get back: id, ref, title, status, state, sha256, expires_on, expires_after_months, sign_by, sealed and signers. Each signer has name, email, method, wave, status, signed_at and answers. Where the agreement runs out some months after the last signature, expires_on is filled in when the document is sealed.

POST https://app.vamosign.com/v1/bulk_send

Sends the same document to a list of people. Needs Team.

templatestring
The name or slug of a template. VAMOSIGN sends its current version.
document_base64string
The PDF, base64-encoded. Use this when you give no template.
filenamestring
The name of the file. If you leave it out, it is dokument.pdf.
mode"separate" | "shared"
separate: each person signs their own copy, and each copy gets its own certificate. This is the default. shared: everyone signs one document.
recipientsarrayrequired
The people the document goes to, one object each:
namestring
The person's name. If you leave it out, VAMOSIGN uses the part of their address before the @.
emailstringrequired
Where VAMOSIGN sends the link. VAMOSIGN skips a person without a valid address.
phonestring
A mobile number with its country code, such as +47. On Starter and above, VAMOSIGN also sends the link by SMS.
sign_method"simple" | "selfie"
simple: the person types their name. This is the default. selfie: the person takes a photograph of themselves on the signing page.
common_signersarray
People who sign every copy, after its recipient. One object each. The person who made the API key signs last.
namestring
The person's name. If you leave it out, VAMOSIGN uses the part of their address before the @.
emailstringrequired
Where VAMOSIGN sends the link. VAMOSIGN skips a person without a valid address.

You get back: batch, which is the reference of the send, and requests, with one entry per request, like the one send_for_signature gives back.

GET https://app.vamosign.com/v1/check_status

Tells you where one request stands, who has signed, and everything that has happened to it. This is a GET, so put the argument in the address.

request_idstringrequired
The id that send_for_signature gave back. You can also call it id.

You get back: Everything send_for_signature gives back, and events. Each event has at, action, actor and ip. Each of a signer's answers has question and answer.

POST https://app.vamosign.com/v1/request_new_version

Asks everyone who signed an earlier version of a template to sign the current one. Each person gets their own request. Needs Team.

templatestringrequired
The name or slug of the template.

You get back: template and requests, with one entry per request.

POST https://app.vamosign.com/v1/add_signer

Adds one person to a draft or to a request that is out. Where everyone is asked at once, VAMOSIGN writes to the new person straight away. Where people are asked in order, the new person signs last. A company is named when the request is made, not here.

request_idstringrequired
The id that send_for_signature gave back.
namestring
The person's name. If you leave it out, VAMOSIGN uses the part of their address before the @.
emailstringrequired
Where VAMOSIGN sends the link. An address already on the request is refused.
phonestring
A mobile number with its country code, such as +47. On Starter and above, VAMOSIGN also sends the link by SMS.
sign_method"simple" | "selfie"
simple: the person types their name. This is the default. selfie: the person takes a photograph of themselves on the signing page.
localestring
The language VAMOSIGN writes to this person in: en, nb, es. If you leave it out, VAMOSIGN uses your workspace's language.

You get back: The request as send_for_signature gives it back, with the new person in signers.

POST https://app.vamosign.com/v1/send_reminder

Sends the invitation again to everyone whose turn it is to sign. The person who made the API key is never reminded.

request_idstringrequired
The id that send_for_signature gave back.

You get back: The request as send_for_signature gives it back, and reminded: how many people VAMOSIGN wrote to.

POST https://app.vamosign.com/v1/cancel_request

Withdraws a request that is not finished. Nobody can sign it after that. A request everyone has signed stays as it is.

request_idstringrequired
The id that send_for_signature gave back.

You get back: The request as send_for_signature gives it back, with status cancelled.

GET https://app.vamosign.com/v1/get_document

Gives you a link to the file: the sealed PDF once everyone has signed, the original before that. The link works for ten minutes and needs no key. This is a GET, so put the argument in the address.

request_idstringrequired
The id that send_for_signature gave back.

You get back: id, ref, sealed, filename, content_type, bytes, sha256, url and expires_at. sha256 is the checksum of the file the link gives you.

GET https://app.vamosign.com/v1/get_evidence

Gives you everything VAMOSIGN recorded about one request as one JSON document, to keep beside the signed file: the checksums, the record code, every signer with method, time, IP address and browser, their answers, and the whole event log. This is a GET, so put the argument in the address.

request_idstringrequired
The id that send_for_signature gave back.

You get back: evidence (the name of the format, vamosign-evidence-v1), generated_at, request, document, record, signers and events.

When VAMOSIGN refuses a REST call, it answers 422 and an error code: no_signers, no_document, unknown_template, unknown_who, not_found, already_ended, not_out, link_closed, not_editable, already_on_request, purged, reminded_recently or sending_paused. On a plan that does not hold the action, the code is tier_required, with the plan that does and the address of the plan page. A missing or revoked key gets 401.