Segment Public API
✓ Official Vendor SpecMarketingSeo Sembearer30 EndpointsREST
For Agents
Programmatically create source, list sources. Covers 30 operations with bearer authentication.
Use for: I need to source, I want to sources, Search for source, Find all source
Not supported: Does not handle payments, communications, or crm — use for marketing only.
The Segment Public API allows you to manage Segment Workspaces and their resources including Sources, Destinations, Warehouses, Spaces, and more. The API exposes 30 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Segment Public API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Segment Public 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 Public API.
Create Source
List Sources
Get Source
Update Source
Delete Source
Add Labels to Source
Replace Labels in Source
Use Cases
Patterns agents use Segment Public API for, with concrete tasks.
★ Marketing Operations
Use the Segment Public API to perform marketing operations programmatically. The API provides 30 endpoints covering core functionality including create source, list sources, get source.
Call POST /sources to create source
Automated Sources Management
Automate sources operations by combining multiple Segment Public API endpoints. Agents can list sources and then get source in a single workflow.
Call GET /sources to list sources, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Segment Public API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'create source', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
30 endpoints — the segment public api allows you to manage segment workspaces and their resources including sources, destinations, warehouses, spaces, and more.
METHOD
PATH
DESCRIPTION
POST
/sources
Create Source
GET
/sources
List Sources
GET
/sources/{sourceId}
Get Source
PATCH
/sources/{sourceId}
Update Source
DELETE
/sources/{sourceId}
Delete Source
POST
/sources/{sourceId}/labels
Add Labels to Source
PUT
/sources/{sourceId}/labels
Replace Labels in Source
POST
/sources/{sourceId}/write-keys
Create Write Key for Source
POST
/sources
Create Source
GET
/sources
List Sources
GET
/sources/{sourceId}
Get Source
PATCH
/sources/{sourceId}
Update Source
DELETE
/sources/{sourceId}
Delete Source
POST
/sources/{sourceId}/labels
Add Labels to Source
PUT
/sources/{sourceId}/labels
Replace Labels in Source
POST
/sources/{sourceId}/write-keys
Create Write Key for Source
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Segment Public API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'create source') and Jentic returns the matching Segment Public API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Segment Public API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Segment Public API through Jentic.
What authentication does the Segment Public API use?
The Segment Public API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I create source with the Segment Public API?
Yes. Use the POST /sources endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Segment Public API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create source through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create source'. Jentic returns the matching Segment Public API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Segment Public API have?
The Segment Public API exposes 30 endpoints covering sources, destinations, warehouses operations.
GET STARTED