Segment API
★ Only Publicly Available OpenAPI DocumentAnalyticsData Pipelinesbearer14 EndpointsREST
For Agents
Configure data collection sources, manage event routing destinations, enforce tracking plans, and audit customer data pipeline changes programmatically.
Use for: I need to create a new source for my iOS application in Segment, I want to list all destinations connected to a specific source, Get the configuration details of a destination by its ID, Check whether a tracking plan is enforcing schema validation on my source
Not supported: Does not handle event analytics querying, dashboards, or visualization — use for data collection routing and pipeline configuration only.
Jentic publishes the only available OpenAPI specification for Segment API, keeping it validated and agent-ready. Configure and manage the customer data infrastructure that collects events from sources, routes them to destinations, and enforces data quality through tracking plans. The API provides programmatic control over sources, destinations, warehouses, tracking plans, functions, spaces, users, and audit logs — enabling teams to treat their data pipeline as code.
Install Jentic One Beta
Connect the Segment API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Segment API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Segment API.
Provision and configure event collection sources for web, mobile, and server-side applications
Connect and manage destinations that receive routed event data from sources
Define tracking plans that validate event schemas before data reaches destinations
Query warehouse sync configurations for data lake and analytics database connections
Deploy custom functions that transform or route events in-flight within the pipeline
Retrieve audit event logs showing who changed pipeline configuration and when
Use Cases
Patterns agents use Segment API for, with concrete tasks.
★ AI Agent Data Pipeline Management
AI agents configure and monitor Segment's customer data infrastructure programmatically — creating sources, connecting destinations, and deploying tracking plans without manual UI interaction. Through Jentic, an agent discovers the needed pipeline operation by intent, receives the schema, and executes configuration changes directly. This enables infrastructure-as-code patterns for data pipelines managed by automated systems.
Create a new JavaScript source via POST /sources, then connect a BigQuery destination via POST /destinations with the source ID
Source and Destination Configuration
Programmatically create, list, and inspect event collection sources and their connected destinations. Sources represent data origins (websites, mobile apps, servers), while destinations are the tools that receive routed events (analytics platforms, warehouses, marketing tools). The API enables teams to manage hundreds of source-destination connections at scale without manual UI configuration.
GET all sources from /sources, then for the first source retrieve its connected destinations via GET /destinations
Tracking Plan Governance
Enforce data quality by defining tracking plans that specify which events and properties are expected from each source. The tracking plans endpoint lets teams create plans, attach them to sources, and ensure that only validated events flow downstream. Invalid events can be blocked or flagged, preventing data quality issues from propagating to warehouses and analytics tools.
List all tracking plans via GET /tracking-plans, then create a new tracking plan via POST /tracking-plans with rules for 'page_viewed' and 'order_completed' events
Data Pipeline Audit and Compliance
Query the audit events endpoint to track who made changes to pipeline configuration, when changes occurred, and what was modified. This supports compliance requirements, debugging pipeline issues by correlating config changes with data anomalies, and maintaining a full audit trail of workspace activity across all team members.
GET audit events from /audit-events for the last 7 days and return all configuration changes made to sources and destinations
Key Endpoints
14 endpoints — jentic publishes the only available openapi specification for segment api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/sources
List all configured event collection sources
POST
/sources
Create a new data collection source
GET
/destinations
List all configured event routing destinations
POST
/destinations
Connect a new destination to receive events
GET
/tracking-plans
List tracking plans for schema governance
POST
/tracking-plans
Create a new tracking plan with event rules
GET
/warehouses
List warehouse sync configurations
GET
/audit-events
Retrieve pipeline configuration audit logs
GET
/sources
List all configured event collection sources
POST
/sources
Create a new data collection source
GET
/destinations
List all configured event routing destinations
POST
/destinations
Connect a new destination to receive events
GET
/tracking-plans
List tracking plans for schema governance
POST
/tracking-plans
Create a new tracking plan with event rules
GET
/warehouses
List warehouse sync configurations
GET
/audit-events
Retrieve pipeline configuration audit logs
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Segment Bearer tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw workspace tokens never enter the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'create a new event source') and Jentic returns matching Segment operations with their input schemas, so the agent can configure data pipelines without browsing docs.
Time to first call
Direct Segment API integration: 1-2 days for token setup, endpoint discovery, and pipeline configuration. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Segment API through Jentic.
Why is there no official OpenAPI spec for Segment API?
Segment does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Segment API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Segment API use?
The Segment API uses Bearer token authentication. You generate a Personal Access Token or workspace token from the Segment app and include it in the Authorization header as 'Bearer {token}'. Through Jentic, your token is stored encrypted in the credential vault and agents receive scoped access without the raw token entering their context.
Can I create sources and destinations programmatically with the Segment API?
Yes. POST /sources creates a new event collection source (web, mobile, or server). POST /destinations connects a new tool to receive events from a source. Both endpoints accept configuration objects specifying the source/destination type and settings.
What are the rate limits for the Segment API?
The Segment Config API allows up to 100 requests per second per workspace on business plans. Each endpoint returns rate limit headers (X-RateLimit-Limit, X-RateLimit-Remaining) so you can implement backoff logic. Read operations have higher limits than write operations.
How do I enforce data quality with tracking plans through Jentic?
Search Jentic for 'enforce event schema validation' to discover the /tracking-plans operations. Create a tracking plan via POST /tracking-plans with event rules that specify required properties and types, then attach it to a source. Events that violate the plan can be blocked or flagged. Install with pip install jentic.
Can I query audit logs for pipeline configuration changes?
Yes. The GET /audit-events endpoint returns a chronological log of all workspace changes including source creation, destination modification, user permission changes, and tracking plan updates. Filter by date range and event type to find specific changes.
How do I deploy custom event transformation functions?
POST /functions creates a custom function that executes JavaScript code on events as they flow through the pipeline. Functions can filter PII, transform event shapes, or conditionally route events. GET /functions lists all deployed functions with their configuration and status.
GET STARTED