Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Knock (BYOK) — connector documentation

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

What Knock (BYOK) is for

Knock (BYOK) lets an AI assistant read your own Knock data through the Knock API with a key you supply (secret API key (starts with sk_)). Read-only: 6 tools (list_messages, get_message, list_users, get_user, list_objects, get_object). 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 api.knock.app. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Knock. Knock 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 Knock notifications failed to deliver recently?"
  • "What happened to this Knock message?"
  • "Which users exist in my Knock environment?"
  • "What are the details of Knock user user_123?"
  • "Which objects are in my Knock projects collection?"
  • "What are the properties of Knock object project-1 in projects?"

What it does

  • list_messages: List notification messages sent through Knock, with delivery status, engagement status, recipient, channel and the workflow that produced each. Cursor pagination.
  • get_message: Get one Knock message by ID: delivery and engagement status, recipient, channel, workflow and timestamps (payload data not returned).
  • list_users: List users (notification recipients) with ID, name, email and timestamps. Cursor pagination.
  • get_user: Get one Knock user by ID: name, email and timestamps.
  • list_objects: List the objects of one collection (non-user recipients such as projects or teams) with their properties. Cursor pagination.
  • get_object: Get one Knock object by collection and ID, with its properties.

BYOK key

You bring your own Knock secret API key (starts with sk_) (https://dashboard.knock.app/). 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 api.knock.app 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 Knock API (api.knock.app) with a BYOK key; documentation: https://docs.knock.app/api-reference/overview. 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 Knock. Knock 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 Knock account.

Built for: Worldwide. Languages: English.