Sinch Conversation (BYOK)

Sinch Conversation (BYOK) — connector documentation

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

What Sinch Conversation (BYOK) is for

Sinch Conversation (BYOK) lets an AI assistant read your own Sinch Conversation data through the Sinch Conversation API with a key you supply (access key ID). Read-only: 6 tools (list_apps, get_app, list_conversations, list_recent_conversations, list_messages, get_project_settings). 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 *.conversation.api.sinch.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Sinch Conversation. Sinch Conversation 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 Conversation API apps do I have in my Sinch project?"
• "What is the retention policy of my Sinch Conversation app?"
• "Which conversations are active in my Sinch app?"
• "Which Sinch conversations had messages most recently?"
• "How many Sinch Conversation messages came in over WhatsApp this week?"
• "Are unified contact ids enabled in my Sinch project?"

What it does

• list_apps: List the Conversation API apps of a project with processing mode, retention policy and rate limits. Channel credentials are not returned.
• get_app: Get one Conversation API app's processing mode, retention policy and rate limits (no channel credentials).
• list_conversations: List conversations of an app or a contact (one of app_id or contact_id is required by the API), with active flag and channel. Up to 20 per page.
• list_recent_conversations: List an app's conversations ordered by latest message time, each with its most recent message's metadata (direction, time, ids). Up to 50 per page.
• list_messages: List message metadata (id, direction, time, conversation, contact, channel) filtered by app, conversation, contact, channel or time window; message bodies and recipient addresses are not returned. Up to 1000 per page.
• get_project_settings: Get project-level Conversation API settings such as whether unified contact ids are enabled.

BYOK key

You bring your own Sinch Conversation access key ID (https://dashboard.sinch.com/settings/access-keys). 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 *.conversation.api.sinch.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.sinch.com/docs/conversation/api-reference/conversation (the API this connector calls, with a BYOK key)

Live from the Sinch Conversation API (*.conversation.api.sinch.com) with a BYOK key; documentation: https://developers.sinch.com/docs/conversation/api-reference/conversation. 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 Sinch Conversation. Sinch Conversation 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 Sinch Conversation account.

Built for: Worldwide. Languages: English.

Sinch Conversation (BYOK) — Privacy Policy

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

What Sinch Conversation (BYOK) is. Sinch Conversation (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Sinch Conversation data: Read your Sinch Conversation API apps, conversations and message metadata (no message content or credentials) with your own access keys. You bring your own Sinch Conversation access key ID; the assistant sends it to us with each request.

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

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

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

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

Sinch Conversation (BYOK) — Terms of Service

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

1. The Service. Sinch Conversation (BYOK) provides: Read your Sinch Conversation API apps, conversations and message metadata (no message content or credentials) with your own access keys. 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 Sinch Conversation credentials and only access data you are allowed to access. Sinch Conversation's terms apply to your use of Sinch Conversation; 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 Sinch Conversation. Sinch Conversation 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 Sinch Conversation returns, lightly trimmed; it may be incomplete, delayed or changed by Sinch Conversation. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Sinch Conversation 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 Sinch Conversation'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; Sinch Conversation 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 Sinch Conversation 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 Sinch Conversation 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-sinch-conversation

Sinch Conversation (BYOK) support

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

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