Hevo Data (BYOK)

Hevo Data (BYOK) — connector documentation

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

What Hevo Data (BYOK) is for

Hevo Data (BYOK) lets an AI assistant read your own Hevo Data data through the Hevo Data API with a key you supply (Hevo API key). Read-only: 11 tools (list_pipelines, get_pipeline, get_pipeline_schedule, list_pipeline_objects, get_pipeline_object_stats, list_event_types, list_destinations, get_destination, get_destination_table_stats, list_models, list_workflows). 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 us.hevodata.com, us2.hevodata.com, eu.hevodata.com, in.hevodata.com, asia.hevodata.com, au.hevodata.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Hevo Data. Hevo Data 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 Hevo pipelines are failing right now?"
• "Show me the details of Hevo pipeline 1"
• "How often does Hevo pipeline 1 run?"
• "Which objects in Hevo pipeline 1 have failed events?"
• "How many events did the orders object of Hevo pipeline 1 ingest recently?"
• "Which event types of Hevo pipeline 1 are unmapped?"

What it does

• list_pipelines: List ELT pipelines with status, health, source name and type, destination, last and next run time and schedule.
• get_pipeline: Get one pipeline: status, health, source and destination summary, schedule, priority and auto-mapping.
• get_pipeline_schedule: Get the schedule options of a pipeline: type, cron or frequency and the allowed frequency range.
• list_pipeline_objects: List the objects (tables, files, streams) a pipeline ingests with status, last run time and position; can filter by a status category or name text.
• get_pipeline_object_stats: Get event counts per processing stage for one pipeline object over the last N minutes (default 120).
• list_event_types: List the event types of a streaming pipeline with auto-mapping setting and mapping status.
• list_destinations: List warehouse destinations with type, status, health, failure reason and schedule.
• get_destination: Get one destination: type, status, health, failure reason and schedule.
• get_destination_table_stats: Get event counts per processing stage for one destination table over the last N minutes (default 120).
• list_models: List SQL transformation models with destination, output table, load type, status, last run status and last failure message.
• list_workflows: List workflows with status, schedule, last run time and status and last failure message.

BYOK key

You bring your own Hevo Data Hevo API key (https://api-docs.hevodata.com/reference/getallpipelines). 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 us.hevodata.com, us2.hevodata.com, eu.hevodata.com, in.hevodata.com, asia.hevodata.com, au.hevodata.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

Read-only: pipeline configuration blocks (which can hold source connection details) are not returned.

Data sources

• https://api-docs.hevodata.com/reference/getallpipelines (the API this connector calls, with a BYOK key)

Live from the Hevo Data API (us.hevodata.com, us2.hevodata.com, eu.hevodata.com, in.hevodata.com, asia.hevodata.com, au.hevodata.com) with a BYOK key; documentation: https://api-docs.hevodata.com/reference/getallpipelines. 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 Hevo Data. Hevo Data 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 Hevo Data account.

Built for: Worldwide. Languages: English.

Hevo Data (BYOK) — Privacy Policy

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

What Hevo Data (BYOK) is. Hevo Data (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Hevo Data data: Read your Hevo Data pipelines, destinations, objects, transformation models and workflows with your own API key and secret. You bring your own Hevo Data Hevo API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Hevo Data 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 us.hevodata.com, us2.hevodata.com, eu.hevodata.com, in.hevodata.com, asia.hevodata.com, au.hevodata.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 Hevo Data 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 Hevo Data receives. The request we make on your behalf, including the key and the arguments, under Hevo Data's own terms and privacy policy. Hevo Data acts at your direction and is the only recipient of the data of your request besides our hosting provider.

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

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

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

Hevo Data (BYOK) — Terms of Service

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

1. The Service. Hevo Data (BYOK) provides: Read your Hevo Data pipelines, destinations, objects, transformation models and workflows with your own API key and secret. 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 Hevo Data credentials and only access data you are allowed to access. Hevo Data's terms apply to your use of Hevo Data; 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 Hevo Data. Hevo Data 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 Hevo Data returns, lightly trimmed; it may be incomplete, delayed or changed by Hevo Data. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Hevo Data 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 Hevo Data'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; Hevo Data 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 Hevo Data 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 Hevo Data 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-hevo

Hevo Data (BYOK) support

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

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