SignRequest (BYOK)

SignRequest (BYOK) — connector documentation

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

What SignRequest (BYOK) is for

SignRequest (BYOK) lets an AI assistant read your own SignRequest data through the SignRequest API with a key you supply (SignRequest API token). Read-only: 8 tools (list_templates, get_template, list_teams, get_team, list_documents, get_document, list_events, list_webhooks). 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 signrequest.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by SignRequest. SignRequest 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 SignRequest templates do I have?"
• "Show SignRequest template 9b2f2504-4f89-11d3-9a0c-0305e82c3301"
• "Which SignRequest teams am I in?"
• "Show the SignRequest team acme"
• "Which SignRequest documents are still waiting to be signed?"
• "What is the status of SignRequest document 3f2504e0-4f89-11d3-9a0c-0305e82c3301?"

What it does

• list_templates: List document templates with name, who-can-use setting and owning team (signer roles are not returned).
• get_template: Get one template's name, who-can-use setting and owning team.
• list_teams: List the teams the token's user belongs to with name, subdomain, sandbox flag and retention date.
• get_team: Get one team's name, subdomain, sandbox flag and retention date (members and callback URLs are not returned).
• list_documents: List documents with status, team, template, sandbox and expiry settings (names, people and contents are not returned); filter by status.
• get_document: Get one document's status, team, template and expiry settings (names, people and contents are not returned).
• list_events: List the event log with event type, status, webhook delivery flag, delivery time and callback status code (document and signer details are not returned).
• list_webhooks: List webhook subscriptions with name, event type, integration and creation time (callback URLs are not returned).

BYOK key

You bring your own SignRequest SignRequest API token (https://signrequest.com/#/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 signrequest.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://github.com/SignRequest/signrequest-python-client (the API this connector calls, with a BYOK key)

Live from the SignRequest API (signrequest.com) with a BYOK key; documentation: https://github.com/SignRequest/signrequest-python-client. 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 SignRequest. SignRequest 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 SignRequest account.

Built for: Worldwide. Languages: English.

SignRequest (BYOK) — Privacy Policy

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

What SignRequest (BYOK) is. SignRequest (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own SignRequest data: Read your SignRequest templates, teams, document statuses, webhook subscriptions and event delivery log with your own API token. You bring your own SignRequest SignRequest API token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one SignRequest 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 signrequest.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 SignRequest 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 SignRequest receives. The request we make on your behalf, including the key and the arguments, under SignRequest's own terms and privacy policy. SignRequest acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer SignRequest 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 SignRequest 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. SignRequest (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 SignRequest at any time to end all access.

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

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

SignRequest (BYOK) — Terms of Service

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

1. The Service. SignRequest (BYOK) provides: Read your SignRequest templates, teams, document statuses, webhook subscriptions and event delivery log with your own API 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 SignRequest credentials and only access data you are allowed to access. SignRequest's terms apply to your use of SignRequest; 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 SignRequest. SignRequest 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 SignRequest returns, lightly trimmed; it may be incomplete, delayed or changed by SignRequest. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your SignRequest 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 SignRequest'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; SignRequest 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 SignRequest 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 SignRequest 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-signrequest

SignRequest (BYOK) support

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

• MCP endpoint: https://byok-signrequest.connectorbay.com/mcp
• REST API: https://byok-signrequest.connectorbay.com/openapi.json
• Live status: https://byok-signrequest.connectorbay.com/health

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. SignRequest (BYOK) never asks for them.