Beamer (BYOK) — connector documentation
- MCP endpoint:
https://byok-beamer.connectorbay.com/mcp - REST API:
POST https://byok-beamer.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-beamer.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Beamer Beamer API key, sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-beamer.connectorbay.com/health· Tool schemas:https://byok-beamer.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-beamer · agent@connectorbay.com
What Beamer (BYOK) is for
Beamer (BYOK) lets an AI assistant read your own Beamer data through the Beamer API with a key you supply (Beamer API key). Read-only: 8 tools (list_posts, count_posts, get_post, list_feature_requests, count_feature_requests, get_feature_request, list_nps_scores, count_nps_responses). 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.getbeamer.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Beamer. Beamer 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:
- "What posts did I publish in Beamer and how many people viewed them?"
- "How many posts have I published in Beamer?"
- "Show Beamer post 123"
- "Which feature requests are under review in Beamer?"
- "How many feature requests did Beamer receive?"
- "Show Beamer feature request 123"
What it does
list_posts: List Beamer changelog posts (newest first) with dates, category, publish state, translations and engagement counts (views, unique views, clicks, feedback and reactions). Calls do not record views.count_posts: Count Beamer changelog posts, optionally by date range, category, language, published or archived state.get_post: Get one Beamer changelog post by ID with its translations, publish state and engagement counts.list_feature_requests: List Beamer feature requests with category, status, translations, vote and comment counts. Requester names, emails and custom attributes are not returned.count_feature_requests: Count Beamer feature requests, optionally by date range, category, status or visibility.get_feature_request: Get one Beamer feature request by ID with its translations, category, status and vote and comment counts.list_nps_scores: List Beamer NPS responses with date, score (0 to 10) and the written feedback. User names and emails are not returned.count_nps_responses: Count Beamer NPS responses, optionally within a date range or score range.
BYOK key
You bring your own Beamer Beamer API key (https://app.getbeamer.com/settings). 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.getbeamer.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
Beamer counts API calls against a monthly plan allowance and bills overage beyond it. Names and email addresses of users are left out of every answer.
Data sources
- https://getbeamer-api.pages.dev/ (the API this connector calls, with a BYOK key)
Live from the Beamer API (api.getbeamer.com) with a BYOK key; documentation: https://getbeamer-api.pages.dev/. 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 Beamer. Beamer 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 Beamer account.
Built for: Worldwide. Languages: English.