{
 "categories": [
  "documents",
  "identity"
 ],
 "deployment": "saas",
 "evidence": [
  {
   "date": "2026-10-06",
   "fact": "homepage",
   "note": "Visma Sign presents hosted electronic signing and contract storage, and says e-signing can be integrated with an API.",
   "source": "https://vismasign.com/",
   "tier": "declared"
  },
  {
   "date": "2026-10-06",
   "fact": "vendor",
   "note": "The footer names Visma Solutions Oy in Lappeenranta. The product name on the page is Visma Sign.",
   "source": "https://vismasign.com/",
   "tier": "declared"
  },
  {
   "date": "2026-10-06",
   "fact": "deployment",
   "note": "Signing and the contract archive are offered as a hosted service with a trial. No self-host edition is described.",
   "source": "https://vismasign.com/",
   "tier": "declared"
  },
  {
   "date": "2026-10-06",
   "fact": "platforms[0]",
   "note": "Documents are created and stored in the Visma Sign web service. This pass did not open a native app store page.",
   "source": "https://vismasign.com/",
   "tier": "declared"
  },
  {
   "date": "2026-10-06",
   "fact": "license",
   "note": "The trial includes 5 free signatures without a card. The page says to upgrade when the trial ends, so the license is commercial.",
   "source": "https://vismasign.com/",
   "tier": "declared"
  },
  {
   "date": "2026-10-06",
   "fact": "modalities.api.exists",
   "note": "Visma Sign API v1 is documented for automating collection of electronic signatures on documents.",
   "source": "https://sign.visma.net/api/docs/v1/",
   "tier": "declared"
  },
  {
   "date": "2026-10-06",
   "fact": "modalities.api.kinds[0]",
   "note": "Documented operations are HTTPS JSON calls such as POST /api/v1/document/ and GET /api/v1/document/{uuid}.",
   "source": "https://sign.visma.net/api/docs/v1/",
   "tier": "declared"
  },
  {
   "date": "2026-10-06",
   "fact": "modalities.api.auth[0]",
   "note": "Organisation authentication is an Authorization header beginning with Onnistuu, the client identifier, and a base64 SHA-512 HMAC of the request. The secret is a 32-byte key delivered base64-encoded.",
   "source": "https://sign.visma.net/api/docs/v1/",
   "tier": "declared"
  },
  {
   "date": "2026-10-06",
   "fact": "modalities.api.coverage",
   "note": "The API creates documents, adds one PDF, creates invitations, and reads status. A document holds one file under 15 MB. Credentials come from support, so coverage is partial.",
   "source": "https://sign.visma.net/api/docs/v1/",
   "tier": "declared"
  },
  {
   "date": "2026-10-06",
   "fact": "modalities.api.docs",
   "note": "Opened the Visma Sign API v1 reference, including prerequisites, the HMAC scheme, and the document and invitation flows.",
   "source": "https://sign.visma.net/api/docs/v1/",
   "tier": "declared"
  },
  {
   "date": "2026-10-06",
   "fact": "modalities.mcp.first_party",
   "note": "The API v1 page does not document an MCP server. That silence does not establish absence, so first_party stays unknown.",
   "source": "https://sign.visma.net/api/docs/v1/",
   "tier": "declared"
  },
  {
   "date": "2026-10-06",
   "fact": "modalities.mcp.verdict",
   "note": "No MCP implementation was established on the vendor pages opened. The verdict stays unknown.",
   "source": "https://sign.visma.net/api/docs/v1/",
   "tier": "declared"
  },
  {
   "date": "2026-10-06",
   "fact": "modalities.data_access.export[0]",
   "note": "GET /api/v1/document/{uuid}/files/0 returns the file content. The introduction says the file is a PDF.",
   "source": "https://sign.visma.net/api/docs/v1/",
   "tier": "declared"
  },
  {
   "date": "2026-10-06",
   "fact": "modalities.data_access.import[0]",
   "note": "POST /api/v1/document/{uuid}/files adds the PDF to be signed. The introduction limits a document to one PDF under 15 MB.",
   "source": "https://sign.visma.net/api/docs/v1/",
   "tier": "declared"
  },
  {
   "date": "2026-10-06",
   "fact": "modalities.rpa.ui_stack[0]",
   "note": "Agreements are created and stored in the Visma Sign web service. No UI probe was run.",
   "source": "https://vismasign.com/",
   "tier": "declared"
  },
  {
   "date": "2026-10-06",
   "fact": "modalities.rpa.drivability",
   "note": "No repeatable UI probe exists. The API documentation establishes a non-browser path, so drivability stays unknown.",
   "source": "https://sign.visma.net/api/docs/v1/",
   "tier": "declared"
  },
  {
   "date": "2026-10-06",
   "fact": "modalities.computer_use.viability",
   "note": "No computer-use probe artifact was produced. Viability stays unknown.",
   "source": "https://vismasign.com/",
   "tier": "declared"
  },
  {
   "date": "2026-10-06",
   "fact": "modalities.agent_docs.llms_txt",
   "note": "The opened pages are the product site and API reference. This pass did not open an llms.txt file, so the field stays unknown.",
   "source": "https://sign.visma.net/api/docs/v1/",
   "tier": "declared"
  },
  {
   "date": "2026-10-06",
   "fact": "verdict.best_path",
   "note": "API v1 is the documented way to collect signatures without the browser. It is the only scored path.",
   "source": "https://sign.visma.net/api/docs/v1/",
   "tier": "declared"
  },
  {
   "date": "2026-10-06",
   "fact": "verdict.scores.api",
   "note": "The reference covers create, file upload, invitations, and signed-file download with HMAC auth. Support-issued credentials and the one-PDF limit keep the score at 6.",
   "source": "https://sign.visma.net/api/docs/v1/",
   "tier": "declared"
  },
  {
   "date": "2026-10-06",
   "fact": "freshness.watch[0].url",
   "note": "Opened Visma Sign API v1, including authentication and the document file routes.",
   "source": "https://sign.visma.net/api/docs/v1/",
   "tier": "declared"
  },
  {
   "date": "2026-10-06",
   "fact": "freshness.watch[1].url",
   "note": "Opened the Visma Sign homepage, including the trial and the API mention.",
   "source": "https://vismasign.com/",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-10-06",
  "volatility": "medium",
  "watch": [
   {
    "type": "docs",
    "url": "https://sign.visma.net/api/docs/v1/"
   },
   {
    "type": "docs",
    "url": "https://vismasign.com/"
   }
  ]
 },
 "homepage": "https://vismasign.com/",
 "id": "visma-sign",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": "unknown"
  },
  "api": {
   "auth": [
    "onnistuu-hmac"
   ],
   "coverage": "partial",
   "docs": "https://sign.visma.net/api/docs/v1/",
   "exists": true,
   "kinds": [
    "rest"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [
    "pdf"
   ],
   "import": [
    "pdf"
   ]
  },
  "extensibility": {
   "scripting": [],
   "webhooks": "unknown"
  },
  "integrations": {
   "make": "unknown",
   "n8n": "unknown",
   "power_automate": "unknown",
   "zapier": "unknown"
  },
  "mcp": {
   "first_party": "unknown",
   "third_party": [],
   "verdict": "unknown"
  },
  "rpa": {
   "drivability": "unknown",
   "notes": "No repeatable UI probe was run. Visma Sign API v1 creates documents, attaches one PDF, and collects electronic signatures. Credentials are ordered from Visma Sign support.\n",
   "ui_stack": [
    "web-dom"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "Visma Sign",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [
   "docusign",
   "signicat",
   "oneflow",
   "contractbook"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Visma",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 6,
   "cli": null,
   "computer_use": null,
   "integrations": null,
   "mcp": null,
   "overall": 6,
   "rpa": null
  },
  "search": {
   "description": "Visma Sign API v1 creates a document, attaches one PDF, and collects signatures. Requests use an Onnistuu HMAC. Credentials and staging are ordered from Visma Sign support.\n",
   "title": "Visma Sign API v1 for electronic signatures"
  },
  "summary": "Visma Sign is automatable today through Visma Sign API v1 at https://sign.visma.net/api/docs/v1/. An organisation account is required. API credentials and a staging environment are ordered from kumppanit.sign@visma.com. Credentials are a client identifier and a secret key. Organisation requests use an Amazon-style HMAC: the Authorization header is Onnistuu, the client identifier, and a base64 SHA-512 HMAC over the verb, content MD5, content type, date, and path. The API creates a document, adds one PDF file, creates invitations, lists authentication methods, and reads document status. A document currently holds one PDF, under 15 MB in production and 1.5 MB in staging. The signed file is fetched with GET /api/v1/document/{uuid}/files/0. Staging does not require a Finnish, Swedish, or Danish SSN or bank credentials, and Visma says it can differ from production. The public homepage offers a trial of 5 signatures and then an upgrade. The footer names Visma Solutions Oy. No MCP server, SDK, CLI, or webhook contract was established on the pages opened. Connector catalogs were not opened. Computer-use viability is unassessed. The API scores 6 because signature collection is documented and partner-issued credentials plus the single-PDF limit are material constraints.\n"
 }
}