Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Segment Sync and Delivery Health (BYOK) icon

Segment Sync and Delivery Health (BYOK)

Read your Segment Reverse ETL models and sync runs, warehouse sync reports and event delivery metrics (counts by event name, no event payloads) with your own Public API token

Unify Dynamics LLC

Tools10read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderSegment Sync and Delivery Healthunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which Reverse ETL models do we have in Segment?
Tools called
list_reverse_etl_models
Did the latest Reverse ETL syncs in Segment succeed?
Tools called
list_reverse_etl_syncs
What happened in Reverse ETL sync sync_1 in Segment?
Tools called
get_reverse_etl_sync
Are my Segment warehouse syncs healthy?
Tools called
list_warehouse_syncs
Is the Segment connection to warehouse wh_1 working?
Tools called
get_warehouse_connection_state
How many events did Segment deliver to destination dst_1 in the last hour?
Tools called
get_destination_delivery_metrics

About

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.

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.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

10 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data10 tools
  • List reverse etl modelsList Reverse ETL models (SQL queries that read rows from a warehouse to send to destinations) with name, description, enabled flag, source id and…
  • List reverse etl syncsList the sync runs of one Reverse ETL mapping (model plus destination subscription) with status, duration, rows extracted and delivered, failure…
  • Get reverse etl syncGet one Reverse ETL sync run: status, duration, extract and load phase counts (added, updated, deleted, delivered, failed) and error.
  • List warehouse syncsList recent sync reports of every source connected to a warehouse: source, start and end, status, duration, record count and any notices.
  • Get warehouse connection stateCheck whether Segment can currently connect to a warehouse with its saved settings: CONNECTED or FAILED.
  • Get destination delivery metricsGet an event delivery summary for one destination: totals per metric (for example successes, failures, retries) with breakdowns, for a source and…
  • Get events receivedGet 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.
  • Get events failed on ingestGet 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.
  • Get events delivered to destinationGet events successfully delivered to a destination over a time window: totals and a time series per event name and type.
  • Get events failed deliveryGet events that failed to be delivered to a destination over a time window: totals, retries and discard reasons per event name.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-segment-sync-health.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

More like this

More in Other

Exotel (BYOK)

Read your Exotel (India, Singapore region) account balance, ExoPhone numbers, call records and SMS delivery status with your own API key and token

Live · MCP + REST6 tools

Gupshup (BYOK)

Read your Gupshup WhatsApp app templates and business profile with your own API key

Live · MCP + REST5 tools

Tap Payments (BYOK)

Read your Tap Payments (Kuwait, Saudi Arabia, UAE, Bahrain, Qatar, Oman, Egypt) charges, payouts, customers, saved cards and intents with your own secret key

Live · MCP + REST8 tools

Kashier (BYOK)

Read your Kashier (Egypt) transactions, orders, payment links, payouts, balances and settlements with your own secret key and API key

Live · MCP + REST10 tools

MSG91 (BYOK)

Read your MSG91 SMS, OTP, email, voice, WhatsApp and RCS delivery reports, logs, call records and templates with your own auth key

Live · MCP + REST12 tools

Channel Talk (BYOK)

Read your Channel Talk customer chats, messages, customers, team members, groups, tags and campaigns with your own access key and secret

Live · MCP + REST12 tools

Get Segment Sync and Delivery Health (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Segment Sync and Delivery Health Segment Public API access token (read-only role is enough; US region). Create one at https://app.segment.com/goto-my-workspace/settings/access-management, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Segment Sync and Delivery Health. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Segment Sync and Delivery Health.