SignWell (BYOK) — connector documentation
- MCP endpoint:
https://byok-signwell.connectorbay.com/mcp - REST API:
POST https://byok-signwell.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-signwell.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own SignWell SignWell API key, sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-signwell.connectorbay.com/health· Tool schemas:https://byok-signwell.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-signwell · agent@connectorbay.com
What SignWell (BYOK) is for
SignWell (BYOK) lets an AI assistant read your own SignWell data through the SignWell API with a key you supply (SignWell API key). Read-only: 8 tools (get_credentials, get_account, get_document, get_template, get_api_application, list_webhooks, list_bulk_sends, get_bulk_send). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to www.signwell.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by SignWell. SignWell and its logos are trademarks of their owners and are used only to say which service the connector works with.
Ask your assistant things like:
- "Which SignWell account is my API key connected to?"
- "What are the default signing settings of my SignWell account?"
- "What is the status of SignWell document a2c3b8f4-0d1e-4f5a-9b6c-7d8e9f0a1b2c?"
- "Show SignWell template 7f6e5d4c"
- "Show my SignWell API application"
- "Which webhooks are registered in my SignWell account?"
What it does
get_credentials: Show the account the API key belongs to: key owner, role, account and workspace names and plan.get_account: Get the account name, plan and default signing settings (date format, link expiry, allowed signature types, time zone, language).get_document: Get one document by id: name, status, requester, subject, message, dates, expiry, language and test mode flag (recipient details are not returned).get_template: Get one document template by id: name, status, requester, subject, message, link and dates.get_api_application: Get one API application (embedded signing app): name, callback URLs, owner and dates.list_webhooks: List the webhook callback URLs registered for document events in the account.list_bulk_sends: List bulk sends (one template sent to many recipients) with name, status, document counts and creation time.get_bulk_send: Get one bulk send: name, status, how many documents were created and completed, and the templates used.
BYOK key
You bring your own SignWell SignWell API key (https://developers.signwell.com/reference/getting-started-with-your-api-1). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to www.signwell.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.
Data sources
- https://developers.signwell.com/reference (the API this connector calls, with a BYOK key)
Live from the SignWell API (www.signwell.com) with a BYOK key; documentation: https://developers.signwell.com/reference. Endpoints checked against that documentation on 2026-10-16.
What it is not
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by SignWell. SignWell and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your SignWell account.
Built for: Worldwide. Languages: English.