Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
eSignatures (BYOK) icon

eSignatures (BYOK)

Read your eSignatures.com contracts, contract content and placeholder values, and your templates with your own secret token

Unify Dynamics LLC

Tools6read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProvidereSignaturesunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

What is the status of eSignatures contract 1contr11-2222?
Tools called
get_contract
What does the text of eSignatures contract 1contr11-2222 say?
Tools called
get_contract_content
Which placeholder values are filled in on this eSignatures contract?
Tools called
get_contract_placeholder_fields
Which contract templates do I have in eSignatures.com?
Tools called
list_templates
What placeholders does eSignatures template 4templ44-8888 have?
Tools called
get_template
What is the text of eSignatures template 4templ44-8888?
Tools called
get_template_content

About

eSignatures (BYOK) lets an AI assistant read your own eSignatures data through the eSignatures API with a key you supply (eSignatures.com secret token). Read-only: 6 tools (get_contract, get_contract_content, get_contract_placeholder_fields, list_templates, get_template, get_template_content). 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 esignatures.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by eSignatures. eSignatures and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the eSignatures API (esignatures.com) with a BYOK key; documentation: https://esignatures.com/docs/api. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

6 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data6 tools
  • Get contractGet one contract's status, title, metadata, source, test flag, labels and signed PDF link; signer names, emails and phone numbers are not returned.
  • Get contract contentGet a contract's text in Markdown.
  • Get contract placeholder fieldsList the placeholder values (key and the text, Markdown or template that replaces it) currently set on a contract.
  • List templatesList the contract templates with ID and title.
  • Get templateGet one template: title, creation time, placeholder field names and signer field IDs.
  • Get template contentGet a template's text in Markdown.

Information

PublisherUnify Dynamics LLC
CategoryWork & productivity
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-esignatures.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 6 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-esignatures.connectorbay.com/mcp
RESTPOST https://byok-esignatures.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-esignatures.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your eSignatures.com secret token in the X-Upstream-Key header (get one at esignatures.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

eSignatures connector: questions and answers

What is the eSignatures connector?

eSignatures (BYOK) lets an AI assistant read your own eSignatures data through the eSignatures API with a key you supply (eSignatures.com secret… It is a hosted MCP server with 6 tools such as Get contract, Get contract content, Get contract placeholder fields, List templates, Get template, Get template content, published by Unify Dynamics LLC. It is independent and not affiliated with eSignatures.

How do I connect eSignatures to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-esignatures.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-esignatures.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-esignatures.json.

Do I need a eSignatures account or API key?

Yes: this is a bring-your-own-key connector. Create a eSignatures.com secret token at https://esignatures.com/docs/api and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is eSignatures read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the eSignatures connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Delighted (BYOK)

Read your Delighted NPS, CSAT and CES survey responses, people, metrics, bounces, unsubscribes and Autopilot members with your own API key

Live · MCP + REST6 tools

360dialog (BYOK)

Read your 360dialog WhatsApp Business number health, message templates, flows, groups and business profile with your own API key

Live · MCP + REST9 tools

Dialpad (BYOK)

Read your Dialpad business phone data: company, users, offices, departments, contact centers, numbers, contacts, calls and transcripts with your own API key

Live · MCP + REST11 tools

Dialpad Admin Config (BYOK)

Read your Dialpad coaching teams, channels, call labels, dispositions, access control policies, office licenses and plan line counts with your own API key (no staff details)

Live · MCP + REST9 tools

Dialpad Routing (BYOK)

Read your Dialpad call routers, contact center and department routing options, hold queues, live queue status and off-duty statuses with your own API key (no staff details)

Live · MCP + REST8 tools

Discord (BYOK)

Read the servers, channels, roles, members, scheduled events and recent messages your Discord bot can see with your own bot token (read-only; never posts)

Live · MCP + REST12 tools

Documentation

Back to top

eSignatures (BYOK) — connector documentation

  • MCP endpoint: https://byok-esignatures.connectorbay.com/mcp
  • REST API: POST https://byok-esignatures.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-esignatures.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own eSignatures eSignatures.com secret token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-esignatures.connectorbay.com/health · Tool schemas: https://byok-esignatures.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-esignatures · agent@connectorbay.com

What eSignatures (BYOK) is for

eSignatures (BYOK) lets an AI assistant read your own eSignatures data through the eSignatures API with a key you supply (eSignatures.com secret token). Read-only: 6 tools (get_contract, get_contract_content, get_contract_placeholder_fields, list_templates, get_template, get_template_content). 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 esignatures.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by eSignatures. eSignatures 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:

  • "What is the status of eSignatures contract 1contr11-2222?"
  • "What does the text of eSignatures contract 1contr11-2222 say?"
  • "Which placeholder values are filled in on this eSignatures contract?"
  • "Which contract templates do I have in eSignatures.com?"
  • "What placeholders does eSignatures template 4templ44-8888 have?"
  • "What is the text of eSignatures template 4templ44-8888?"

What it does

  • get_contract: Get one contract's status, title, metadata, source, test flag, labels and signed PDF link; signer names, emails and phone numbers are not returned. The vendor asks you not to poll this repeatedly.
  • get_contract_content: Get a contract's text in Markdown.
  • get_contract_placeholder_fields: List the placeholder values (key and the text, Markdown or template that replaces it) currently set on a contract.
  • list_templates: List the contract templates with ID and title.
  • get_template: Get one template: title, creation time, placeholder field names and signer field IDs.
  • get_template_content: Get a template's text in Markdown.

BYOK key

You bring your own eSignatures eSignatures.com secret token (https://esignatures.com/docs/api). 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 esignatures.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

Live from the eSignatures API (esignatures.com) with a BYOK key; documentation: https://esignatures.com/docs/api. 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 eSignatures. eSignatures 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 eSignatures account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

eSignatures (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What eSignatures (BYOK) is. eSignatures (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own eSignatures data: Read your eSignatures.com contracts, contract content and placeholder values, and your templates with your own secret token. You bring your own eSignatures eSignatures.com secret token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one eSignatures call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to esignatures.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If eSignatures rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What eSignatures receives. The request we make on your behalf, including the key and the arguments, under eSignatures's own terms and privacy policy. eSignatures acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer eSignatures gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your eSignatures data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. eSignatures (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at eSignatures at any time to end all access.

Children. eSignatures (BYOK) is a general-audience service operated by the adult using the assistant, under eSignatures's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

eSignatures (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the eSignatures (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. eSignatures (BYOK) provides: Read your eSignatures.com contracts, contract content and placeholder values, and your templates with your own secret token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own eSignatures credentials and only access data you are allowed to access. eSignatures's terms apply to your use of eSignatures; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by eSignatures. eSignatures and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data eSignatures returns, lightly trimmed; it may be incomplete, delayed or changed by eSignatures. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your eSignatures account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent eSignatures's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; eSignatures may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your eSignatures key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action eSignatures takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-esignatures

eSignatures (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. eSignatures (BYOK) never asks for them.

Get eSignatures (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own eSignatures eSignatures.com secret token. Create one at https://esignatures.com/docs/api, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to eSignatures. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with eSignatures.