Analytics
Segment in your product and your AI agents, through one API
The Segment toolkit reads the sources, destinations and warehouses of a workspace in the US region through the Public API, along with delivery metrics, warehouse syncs and the volume of events received. Through Connect, a product or AI agent inspects the customer's data pipeline without building the integration.
15 days to try it. No credit card.
POST https://connect.reportei.com/api/tools/segment_list_sources/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {}
}How it works
From a connected customer to the first Segment call.
- 1
Your customer connects the account
Your system opens a Connect session for the toolkit and your customer connects their Segment account. You get the connection id.
- 2
Your product calls the tool
A POST to /api/tools/{tool}/execute with the connection id and arguments. On success, Connect preserves the app's response status and body.
- 3
Connect handles the rest
It stores the credential encrypted, renews tokens for OAuth connections that support renewal and records executions in an audit trail available through the API.
Use cases
What your product does with Segment.
Pipeline health in your product
Show which destinations receive data from each source and read delivery metrics for a period to spot failing deliveries.
Warehouse sync checks
List the latest syncs of a warehouse with status and duration to check whether the data is arriving.
Event volume for an agent
Let an AI agent read how many events the workspace received per bucket, grouped by source or event name, and explain a drop or spike.
Tools
11 Segment tools
- List sourcesGETLists the sources of the workspace with id, name, slug, enabled, metadata and labels. Returns the first 200, because the connection does not send pagination; pagination.totalEntries tells whether there are more.
- Get sourceGETReturns one source with its settings, write keys, metadata and labels.
- List connected destinationsGETLists the destinations that receive data from one source, with id, name, enabled and metadata. Returns the first 200, because the connection does not send pagination.
- List connected warehousesGETLists the warehouses that receive data from one source. Returns the first 200, because the connection does not send pagination.
- List destinationsGETLists the destinations of the workspace with id, name, enabled, metadata and the sourceId each one belongs to. Returns the first 200, because the connection does not send pagination; pagination.totalEntries tells whether there are more.
- Get destinationGETReturns one destination with its settings, metadata and the sourceId it belongs to.
- Get delivery metricsGETReturns the delivery metrics of one destination for the events of one source in a period, each metric with its total and breakdown. Without dates, it covers the last hour by minute.
- List warehousesGETLists the warehouses of the workspace with id, enabled, metadata and settings. Returns the first 200, because the connection does not send pagination; pagination.totalEntries tells whether there are more.
- Get warehouseGETReturns one warehouse with its settings and metadata.
- List warehouse syncsGETLists the latest syncs of one warehouse, with status and duration, to check whether the data is arriving. Returns the first 200, because the connection does not send pagination.
API key
Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.
Questions about the Segment toolkit
Do I need to build against the Segment API?
No. Connect ships 11 Segment tools, described and ready. Your customer connects the account and your system calls every tool through the same endpoint, with the same request format.
How does my customer connect their Segment account?
With the mode the toolkit accepts: API key. Connect stores the credential encrypted and never returns it to your system.
Does it work with AI agents?
Yes. Each tool's input is described in JSON Schema, which your agent uses directly as a tool definition. The agent picks the tool and the arguments, and your system makes the call to Connect.
Does my customer need a Reportei account?
No. Your customer connects the account on a Connect screen, or your system sends the credential through the API, and they keep using only your product.
See Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
