Buildium Communications (BYOK)

Buildium Communications (BYOK) — connector documentation

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

What Buildium Communications (BYOK) is for

Buildium Communications (BYOK) lets an AI assistant read your own Buildium Communications data through the Buildium Communications API with a key you supply (API key client ID). Read-only: 5 tools (list_announcements, list_message_templates, list_architectural_requests, list_todo_tasks, get_partial_payment_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 api.buildium.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Buildium Communications. Buildium Communications 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 announcements did I send in Buildium this month?"
• "Which message templates exist in Buildium for tenants?"
• "Which architectural requests are pending in Buildium?"
• "Which Buildium to-dos are due this week?"
• "Does Buildium require residents to pay in full?"

What it does

• list_announcements: List announcements with subject, body, announcement and expiration dates and channels; filter by date range or by rental or association.
• list_message_templates: List communication templates with name, description and the type of recipient they are written for.
• list_architectural_requests: List association architectural requests with association, ownership account, name, submission date, status and decision.
• list_todo_tasks: List to-do tasks with title, description, category, property, status, priority and due date.
• get_partial_payment_settings: Show whether Buildium requires resident online payments to be made in full.

BYOK key

You bring your own Buildium Communications API key client ID (https://developer.buildium.com/#section/Getting-Started/Creating-API-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 api.buildium.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.

Notices

Buildium's Open API needs a Premium subscription with the Open API setting turned on and an API key created under Settings > Developer Tools.

Data sources

• https://developer.buildium.com/ (the API this connector calls, with a BYOK key)

Live from the Buildium Communications API (api.buildium.com) with a BYOK key; documentation: https://developer.buildium.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 Buildium Communications. Buildium Communications 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 Buildium Communications account.

Built for: Worldwide. Languages: English.

Buildium Communications (BYOK) — Privacy Policy

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

What Buildium Communications (BYOK) is. Buildium Communications (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Buildium Communications data: Read your Buildium announcements, message templates, architectural requests, to-do tasks and resident payment setting with your own API key. You bring your own Buildium Communications API key client ID; the assistant sends it to us with each request.

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

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

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

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

Buildium Communications (BYOK) — Terms of Service

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

1. The Service. Buildium Communications (BYOK) provides: Read your Buildium announcements, message templates, architectural requests, to-do tasks and resident payment setting 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 Buildium Communications credentials and only access data you are allowed to access. Buildium Communications's terms apply to your use of Buildium Communications; 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 Buildium Communications. Buildium Communications 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 Buildium Communications returns, lightly trimmed; it may be incomplete, delayed or changed by Buildium Communications. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Buildium Communications 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 Buildium Communications'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; Buildium Communications 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 Buildium Communications 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 Buildium Communications 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-buildium-communications

Buildium Communications (BYOK) support

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

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