Send documents for signature from your own system, by API or MCP
Short answer: create an API key in VAMOSign's Developers room and call five 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. 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.
- Once · You
You open Developers in VAMOSign and create an API key for the workspace.
- Once · You
You add a webhook: an address in your system and the events you want, such as document.sealed.
- Case opens · Your system
Your system calls send_for_signature with the document, a title and the signers' names and e-mail addresses. Over REST or as an MCP tool, it is the same action.
- Same second · VAMOSign
VAMOSign answers with the request's id and e-mails each signer their link.
- Later · The signers
The signers sign in the browser, as with any request.
- 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.
- When done · VAMOSign
VAMOSign posts document.sealed. Your system calls check_status with the id to read who signed and when.
- Any time · You
The Developers room shows every webhook delivery, including the ones that failed.
What it costs
send_for_signature and check_status work on every plan, at no charge. bulk_send, create_self_sign_link and request_new_version need Better, 99 kr a month, ex VAT. On a lower plan the API answers which plan they need.
What it does not do
- It does not need an SDK. It is plain REST and the Model Context Protocol.
- It does not let a key act outside its own workspace.
- It does not hide a failed webhook. Every delivery attempt is in the log.
Questions
- What are the five actions?
- send_for_signature, check_status, bulk_send, create_self_sign_link and request_new_version.
- Which webhook events are there?
- signature.completed, document.sealed, request.declined and bulk.started.
- Where is the MCP server?
- POST https://app.vamosign.com/mcp, with the workspace API key as a bearer token.
- Where is the REST API?
- https://app.vamosign.com/v1/, with the same key.