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

Coralogix (BYOK) — connector documentation

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

What Coralogix (BYOK) is for

Coralogix (BYOK) lets an AI assistant read your own Coralogix data through the Coralogix API with a key you supply (Coralogix API key with read permissions for the objects these tools read). Read-only: 7 tools (list_connector_summaries, get_connector_type_counts, list_preset_summaries, list_global_routers, list_outgoing_webhook_summaries, get_outgoing_webhook_type_counts, list_actions). 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.eu1.coralogix.com, api.eu2.coralogix.com, api.us1.coralogix.com, api.us2.coralogix.com, api.us3.coralogix.com, api.ap1.coralogix.com, api.ap2.coralogix.com, api.ap3.coralogix.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Coralogix. Coralogix 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 notification connectors are set up in Coralogix?"
  • "How many connectors of each type does Coralogix have?"
  • "Which notification presets exist in Coralogix?"
  • "Which global notification routers does Coralogix have?"
  • "Which outgoing webhooks are configured in Coralogix?"
  • "How many outgoing webhooks of each type exist in Coralogix?"

What it does

  • list_connector_summaries: List notification connectors (Slack, PagerDuty, generic HTTPS, email and others) with name, type and timestamps; connector settings are not requested.
  • get_connector_type_counts: Count notification connectors per type.
  • list_preset_summaries: List notification presets (message templates) with name, connector type, entity type, preset type (system or custom) and parent preset.
  • list_global_routers: List global notification routers with name, description, disabled flag and routing labels (team, service, environment).
  • list_outgoing_webhook_summaries: List outgoing webhooks with name, type and timestamps; URLs and credentials are not part of the summary.
  • get_outgoing_webhook_type_counts: Count outgoing webhooks per type (Slack, PagerDuty, generic, Jira, Opsgenie and so on).
  • list_actions: List log actions (custom links that open a URL from a log field) with name, description, source type, visibility and creator.

BYOK key

You bring your own Coralogix Coralogix API key with read permissions for the objects these tools read (https://coralogix.com/docs/user-guides/account-management/api-keys/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.eu1.coralogix.com, api.eu2.coralogix.com, api.us1.coralogix.com, api.us2.coralogix.com, api.us3.coralogix.com, api.ap1.coralogix.com, api.ap2.coralogix.com, api.ap3.coralogix.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

Live from the Coralogix API (api.eu1.coralogix.com, api.eu2.coralogix.com, api.us1.coralogix.com, api.us2.coralogix.com, api.us3.coralogix.com, api.ap1.coralogix.com, api.ap2.coralogix.com, api.ap3.coralogix.com) with a BYOK key; documentation: https://coralogix.com/docs/api-reference/. 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 Coralogix. Coralogix 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 Coralogix account.

Built for: Worldwide. Languages: English.