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

Segment Sync and Delivery Health (BYOK) — connector documentation

  • MCP endpoint: https://byok-segment-sync-health.connectorbay.com/mcp
  • REST API: POST https://byok-segment-sync-health.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-segment-sync-health.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Segment Sync and Delivery Health Segment Public API access token (read-only role is enough; US region), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-segment-sync-health.connectorbay.com/health · Tool schemas: https://byok-segment-sync-health.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-segment-sync-health · agent@connectorbay.com

What Segment Sync and Delivery Health (BYOK) is for

Segment Sync and Delivery Health (BYOK) lets an AI assistant read your own Segment Sync and Delivery Health data through the Segment Sync and Delivery Health API with a key you supply (Segment Public API access token (read-only role is enough; US region)). Read-only: 10 tools (list_reverse_etl_models, list_reverse_etl_syncs, get_reverse_etl_sync, list_warehouse_syncs, get_warehouse_connection_state, get_destination_delivery_metrics, get_events_received, get_events_failed_on_ingest, get_events_delivered_to_destination, get_events_failed_delivery). 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.segmentapis.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Segment Sync and Delivery Health. Segment Sync and Delivery Health 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 Reverse ETL models do we have in Segment?"
  • "Did the latest Reverse ETL syncs in Segment succeed?"
  • "What happened in Reverse ETL sync sync_1 in Segment?"
  • "Are my Segment warehouse syncs healthy?"
  • "Is the Segment connection to warehouse wh_1 working?"
  • "How many events did Segment deliver to destination dst_1 in the last hour?"

What it does

  • list_reverse_etl_models: List Reverse ETL models (SQL queries that read rows from a warehouse to send to destinations) with name, description, enabled flag, source id and the query text. Alpha endpoint.
  • list_reverse_etl_syncs: List the sync runs of one Reverse ETL mapping (model plus destination subscription) with status, duration, rows extracted and delivered, failure counts and error codes. Alpha endpoint.
  • get_reverse_etl_sync: Get one Reverse ETL sync run: status, duration, extract and load phase counts (added, updated, deleted, delivered, failed) and error. Alpha endpoint.
  • list_warehouse_syncs: List recent sync reports of every source connected to a warehouse: source, start and end, status, duration, record count and any notices. Rate limited to 2 requests per minute.
  • get_warehouse_connection_state: Check whether Segment can currently connect to a warehouse with its saved settings: CONNECTED or FAILED. Credentials are not returned.
  • get_destination_delivery_metrics: Get an event delivery summary for one destination: totals per metric (for example successes, failures, retries) with breakdowns, for a source and time window. Beta endpoint.
  • get_events_received: Get events successfully received by Segment for a source over a time window: totals and a time series per event name, event type and app version. Beta endpoint.
  • get_events_failed_on_ingest: Get events that failed on ingest for a source over a time window: totals and a time series per event name, event type, discard reason and app version. Beta endpoint.
  • get_events_delivered_to_destination: Get events successfully delivered to a destination over a time window: totals and a time series per event name and type. Beta endpoint.
  • get_events_failed_delivery: Get events that failed to be delivered to a destination over a time window: totals, retries and discard reasons per event name. Beta endpoint.

BYOK key

You bring your own Segment Sync and Delivery Health Segment Public API access token (read-only role is enough; US region) (https://app.segment.com/goto-my-workspace/settings/access-management). 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.segmentapis.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 Segment Sync and Delivery Health API (api.segmentapis.com) with a BYOK key; documentation: https://docs.segmentapis.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 Segment Sync and Delivery Health. Segment Sync and Delivery Health 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 Segment Sync and Delivery Health account.

Built for: Worldwide. Languages: English.