Send the events where your team already looks.
VG·Sign emits an event for everything that happens to an envelope, and exposes the whole signing flow over a REST API. What follows is what is switched on today — a workspace owner sets any of it up in a few minutes without talking to us.
Live today
Every one of these is set up from Settings → Integrations with a URL you generate yourself. No partner programme, no app to get approved, no call with us.
A message in the channel you choose when an envelope is sent, signed, completed or declined.
Create an incoming webhook in your own Slack, paste the URL into Settings → Integrations, tick the events you care about. Nothing to install.
The same events as an Adaptive Card in a Teams channel.
Build a flow from "When a Teams webhook request is received" in Power Automate and paste the URL it gives you.
Envelope events into whatever those tools can reach, which is most things.
Each one hands you a catch-hook URL. Paste it in as a plain HTTPS endpoint — no app to approve on either side.
Create, send, track, remind, void and download — field placement included, so a send never has to pass through our editor.
A workspace bearer token from Settings → Integrations. OpenAPI 3.1 description at /api/v1/openapi.json.
Eighteen envelope events, each POSTed as JSON signed with HMAC-SHA256 so you can prove it came from us.
Add an endpoint in Settings → Integrations, choose the events, and watch the delivery log with response codes and a resend button.
Claude, Claude Code and Cursor can list envelopes, create one from a template, send it and download the signed PDF.
A stdio MCP server that wraps the same REST API. Point your client at it with your workspace token.
Signing inside the CRM: agents sign in once, envelopes are created against their own workspace, events flow back.
OAuth2 single sign-on plus the API. This is the integration VG·Sign was built around.
The signer page inside your own product, in an iframe, with progress reported back to the parent window.
A script tag and an allow-listed origin.
Or wire it up yourself
The API is the integration. Everything above is built on the same public routes you get, and there is nothing reserved for us.
- REST over HTTPS, one bearer token per workspace, documented at /api-docs.
- An OpenAPI 3.1 document at /api/v1/openapi.json — import it straight into Postman or Insomnia, or generate a typed client from it.
- Signed webhooks with a per-endpoint event selection, a delivery log and retries, so you are not polling.
- Every endpoint is scoped to one workspace: an id from another workspace answers 404, not 403.
What we have not built
Direct integrations with Salesforce, HubSpot, Google Drive, Dropbox and the rest are not built, and we would rather say so than draw their logos with “coming soon” underneath. Most of what people want from them is one Zapier or Make scenario away today, and if you need a native one, tell us which — that is how it gets prioritised.
Tell us what you need →