Zenduty (BYOK)

Zenduty (BYOK) — connector documentation

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

What Zenduty (BYOK) is for

Zenduty (BYOK) lets an AI assistant read your own Zenduty data through the Zenduty API with a key you supply (Zenduty API key). Read-only: 12 tools (list_account_members, list_teams, list_services, get_service, list_escalation_policies, list_schedules, list_priorities, list_maintenance_windows, list_incidents, get_incident, list_incident_notes, list_incident_alerts). 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.zenduty.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Zenduty. Zenduty 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:

• "Who are the admins in our Zenduty account?"
• "Which teams do we have in Zenduty?"
• "Which services does the Backend team have in Zenduty?"
• "Show the Production Service of my team in Zenduty"
• "How are escalations set up for the Backend team in Zenduty?"
• "Which on-call schedules does the Backend team have in Zenduty?"

What it does

• list_account_members: List the members of the Zenduty account with role (1 owner, 2 admin, 3 user), time zone, verification flag and join date. Email addresses are not returned.
• list_teams: List the teams of the account with name, owner and creation date.
• list_services: List the services of one team (the things alerts are routed to) with status, escalation policy and maintenance flag.
• get_service: Get one service of a team with timeouts, escalation policy and maintenance flag.
• list_escalation_policies: List the escalation policies of one team with name, repeat count and whether the policy is global.
• list_schedules: List the on-call schedules of one team with name, summary and time zone.
• list_priorities: List the incident priorities defined for one team with name, description and colour.
• list_maintenance_windows: List the maintenance windows of one team with start, end, repeat interval and time zone.
• list_incidents: List incidents matching a filter (status, creation date range, all teams or only the caller's teams), newest first, with title, status, SLA and assignee name. Uses a POST that only reads; follow next for more pages.
• get_incident: Get one incident by number with title, summary, status, urgency, assignee name and acknowledge and resolve times.
• list_incident_notes: List the notes written on one incident with author name and time.
• list_incident_alerts: List the alerts grouped into one incident with summary, message, time and suppressed flag.

BYOK key

You bring your own Zenduty Zenduty API key (https://apidocs.zenduty.com/). 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.zenduty.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://apidocs.zenduty.com/ (the API this connector calls, with a BYOK key)

Live from the Zenduty API (www.zenduty.com) with a BYOK key; documentation: https://apidocs.zenduty.com/. 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 Zenduty. Zenduty 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 Zenduty account.

Built for: Worldwide. Languages: English.

Zenduty (BYOK) — Privacy Policy

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

What Zenduty (BYOK) is. Zenduty (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Zenduty data: Read your Zenduty teams, services, escalation policies, schedules, maintenance windows and incidents with your own API key. You bring your own Zenduty Zenduty API key; the assistant sends it to us with each request.

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

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

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

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

Zenduty (BYOK) — Terms of Service

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

1. The Service. Zenduty (BYOK) provides: Read your Zenduty teams, services, escalation policies, schedules, maintenance windows and incidents with your own API key. 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 Zenduty credentials and only access data you are allowed to access. Zenduty's terms apply to your use of Zenduty; 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 Zenduty. Zenduty 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 Zenduty returns, lightly trimmed; it may be incomplete, delayed or changed by Zenduty. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Zenduty 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 Zenduty'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; Zenduty 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 Zenduty 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 Zenduty 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-zenduty

Zenduty (BYOK) support

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

• MCP endpoint: https://byok-zenduty.connectorbay.com/mcp
• REST API: https://byok-zenduty.connectorbay.com/openapi.json
• Live status: https://byok-zenduty.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. Zenduty (BYOK) never asks for them.