Talon.One Segment API

[Segment](https://segment.com/) is a customer data platform that collects events from your web & mobile apps. Use these endpoints to integrate with Talon.One.

Business capability
Customer Relationship Management BC-420

Operations 13

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

PUT /segment/customer_profile/{customerProfileId} Upsert a customer profile via Segment (deprecated v1) · Upsert customer profile v1 (Segment) #
Ask an LLM
“Is the original v1 Segment customer profile upsert still supported?”
“What did the first Segment profile endpoint do with attributesInfo?”
Tell an agent
Upsert customer profile {customerProfileId} with attributes {attributes} via the deprecated v1 Segment endpoint on {destination-hostname}.
Use the legacy v1 Segment profile upsert for {customerProfileId} on host {destination-hostname}.
PUT /segment/customer_profile_v2/{customerProfileId} Upsert a customer profile via Segment (deprecated v2) · Upsert customer profile v2 (Segment) #
Ask an LLM
“What was the deprecated customer_profile_v2 Segment endpoint used for?”
“Could the old v2 Segment upsert change a profile's audiences as well as attributes?”
Tell an agent
Upsert profile {customerProfileId} with audience changes {audiencesChanges} using the deprecated customer_profile_v2 Segment route on {destination-hostname}.
Call the legacy customer_profile_v2 Segment upsert for {customerProfileId} on {destination-hostname}.
PUT /segment/v2/customer_profiles/{customerProfileId} Update or create a customer profile from Segment · Update customer profile (Segment) #
Ask an LLM
“What is the current way to sync a Segment identify call into a customer profile?”
“Can I skip attributes that don't exist yet when updating a profile from Segment?”
Tell an agent
Update customer profile {customerProfileId} from Segment with attributes {attributes} on {destination-hostname}.
Sync Segment profile {customerProfileId} to {destination-hostname}, skipping unknown attributes: {skipNonExistingAttributes}.
PUT /segment/customer_profiles/{customerProfileId}/audiences Change one profile's audiences from Segment · Update customer profile audiences using external ID (Segment) #
Ask an LLM
“Can I add a single customer to Segment audiences using the Segment audience ID?”
“Does changing one profile's audiences from Segment trigger rules?”
Tell an agent
Update the audiences of profile {customerProfileId} with {data} from Segment on {destination-hostname}.
Remove customer {customerProfileId} from the Segment audiences in {data} via {destination-hostname}.
PUT /segment/customer_profiles/audiences Update audiences for many profiles from Segment · Update audiences in multiple customer profiles (Segment) #
Ask an LLM
“Can I update audience membership for a batch of customers coming from Segment?”
“Are missing customer profiles created when I bulk update audiences from Segment?”
Tell an agent
Bulk update audiences for multiple profiles with {data} from Segment on {destination-hostname}.
Apply Segment audience changes {data} to many customer profiles via the v1 bulk route on {destination-hostname}.
PUT /segment/v2/customer_profiles/audiences Update audiences for many profiles by external ID · Update audiences in multiple customer profiles using external ID (Segment) #
Ask an LLM
“Can I bulk update audiences using the audience ID from the third-party integration?”
“What's the v2 bulk route for Segment audience changes keyed by external ID?”
Tell an agent
Bulk update audiences by external audience ID with {data} on {destination-hostname}.
Apply externally identified audience changes {data} to many profiles via the v2 Segment route on {destination-hostname}.
PUT /segment/event Track a custom event from Segment (deprecated v1) · Track event v1 (Segment) #
Ask an LLM
“How did the deprecated v1 Segment track event endpoint work?”
“Which fields did the original Segment event call require?”
Tell an agent
Send event {eventType} of type {type} for profile {customerProfileId} through the deprecated v1 Segment event route on {destination-hostname}.
Use the legacy Segment event endpoint to track {eventType} ({type}) for {customerProfileId} on {destination-hostname}.
PUT /segment/v2/events Track a custom event from Segment · Track event v2 (Segment) #
Ask an LLM
“How do I trigger promotion rules from a Segment track call?”
“Does the custom event need to exist in the Campaign Manager before Segment sends it?”
Tell an agent
Track Segment event {eventType} for customer {customerProfileId} on {destination-hostname}.
Send event {eventType} with attributes {eventAttributes} from Segment to {destination-hostname}.
POST /segment/audiences Create an audience from Segment · Create audience (Segment) #
Ask an LLM
“How do I bring a Segment audience over so I can target it in rules?”
“What does creating the first audience unlock in the Rule Builder?”
Tell an agent
Create audience {audienceName} with Segment ID {audienceId} on {destination-hostname}.
Register the new Segment audience {audienceId} named {audienceName} via {destination-hostname}.
PUT /segment/audiences/{audienceId} Rename a Segment audience · Update audience (Segment) #
Ask an LLM
“Can I rename an audience that came from Segment?”
“What is required to update an existing Segment audience?”
Tell an agent
Rename Segment audience {audienceId} to {audienceName} on {destination-hostname}.
Update existing Segment audience {audienceId} with name {audienceName} via {destination-hostname}.
DELETE /segment/audiences/{audienceId} Delete a Segment audience · Delete audience (Segment) #
Ask an LLM
“Does deleting a Segment audience also remove its customer associations?”
“How can I drop an audience that Segment created?”
Tell an agent destructive · confirm first
Delete Segment audience {audienceId} on {destination-hostname}.
Remove the Segment-synced audience {audienceId} and its memberships via {destination-hostname}.
PUT /segment/customer_sessions/{customerSessionId} Update a customer session from Segment (deprecated v1) · Update customer session v1 (Segment) #
Ask an LLM
“What did the deprecated v1 Segment customer session endpoint accept?”
“Could the legacy Segment session update send its response to a callback URL?”
Tell an agent
Update session {customerSessionId} with {customerSession} via the deprecated v1 Segment session route on {destination-hostname}.
Use the legacy Segment session endpoint for {customerSessionId} on {destination-hostname}, calling back to {X-Callback-Destination-URI}.
PUT /segment/v2/customer_sessions/{customerSessionId} Update or create a customer session from Segment · Update customer session v2 (Segment) #
Ask an LLM
“How do I send a Segment cart to get the promotions that apply to it?”
“Can Segment session updates include coupon codes and loyalty cards?”
Tell an agent
Update Segment session {customerSessionId} with cart items {cartItems} on {destination-hostname}.
Apply coupon codes {couponCodes} to Segment session {customerSessionId} for profile {profileId} on {destination-hostname}.

Documentation

Specifications

Other Resources

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/talon-one:talon-one-segment-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

talon-one-segment-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  version: ''
  title: Third-party Segment API
  description: Use the Third-party API to exchange data between Talon.One and one of the supported technology partners.
servers:
- url: https://integration.talon.one
security:
- ApiKeyAuth: []
tags:


# --- truncated at 32 KB (121 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/talon-one/refs/heads/main/openapi/talon-one-segment-api-openapi.yml