Connect the services your company runs.

100+ pre-built integrations: every major ad, affiliate and analytics platform, and the CRM, commerce, finance and messaging tools your company runs. Each is declared in your workspace's code and its credential stays with the platform: pipelines, ontology actions and the agent call the service through it without ever holding the key.

pre-built integrations
100+
ad and affiliate platforms
29
categories
11

Not listed? Any other service with an API connects the same way, with a key, an OAuth 2.0 sign-in or a client ID and secret. How it works

All integrations

134 integrations

Advertising

29
Google AdsAccounts and GAQL reporting for spend, clicks and conversions.Meta AdsSpend and results from Facebook and Instagram campaigns.Microsoft AdsBing and Microsoft Advertising accounts, campaigns and reports.TikTok AdsAdvertisers, campaigns and integrated reports.LinkedIn AdsAd accounts, campaigns, analytics and the Conversions API.X AdsAds accounts, campaigns, line items and stats.Pinterest AdsPinterest campaign spend and results.Reddit AdsReddit campaign spend and results.Snapchat AdsSnapchat campaign spend and results.Amazon AdsSponsored products, brands and display spend.Display & Video 360Programmatic spend, impressions and conversions by line item.Campaign Manager 360Impressions, clicks and Floodlight conversions across campaigns.Apple Search AdsCampaign, ad group and keyword spend and installs.The Trade DeskProgrammatic campaign spend, impressions and conversions.CriteoRetargeting and retail media spend, clicks and sales.AdRollRetargeting campaign spend and results.StackAdaptProgrammatic campaign spend, impressions and conversions.TaboolaNative campaign spend, clicks and conversions.OutbrainNative campaign spend, clicks and conversions.AdformProgrammatic campaign spend and delivery.XandrProgrammatic campaign spend and delivery on Microsoft Invest.RTB HouseRetargeting campaign spend and conversions.AppLovinApp campaign spend, installs and revenue.Quora AdsCampaign spend and conversions.Spotify AdsAudio and video campaign spend and delivery.AwinAffiliate transactions, commissions and publisher performance.Impact.comPartner actions, payouts and media partner performance.Rakuten AdvertisingAffiliate transactions, commissions and publisher performance.PartnerStackPartner referrals, customers and payouts.

Not listed? Your agent can connect any API.

If a service has an HTTPS API that takes a key, an OAuth 2.0 sign-in or a client ID and secret, your agent can connect it with one of the generic connections. It is the same declaration the ready-made ones use, and the credential is kept the same way.

  1. 1DeclareYour agent adds the connection to connections/connections.py: the service's API address, and each credential as a Secret. The value itself never goes in the repository.
  2. 2Deploysegmentstream deploy publishes the declaration. The connection appears in the console, waiting for its credential.
  3. 3ConnectPaste the key in the console or with segmentstream connection configure, or sign in for OAuth. The platform keeps the value and attaches it to every request.
connections/connections.py
from segmentstream_connections import ApiKeyConnection, Bearer, Secret connections = (    ApiKeyConnection(        key="billing",        name="Billing",        provider="billing",        headers={"Authorization": Bearer(Secret(label="API key"))},        apis={"v1": "https://api.billing.example.com/v1/"},    ),)
$ segmentstream deploy
$ segmentstream connection configure billing
Inside SegmentStream

Connected once, used everywhere.

Connections are declared in your repository and authorised in the console. The credentials stay with the platform; apps, pipelines, workflows and the agent use them under the same roles.

segmentstream.com
The console's connections page: the 43 connections declared in our workspace's code, here the public reference lists of AI and search crawlers, each connected, with the key it is declared under
Connections declared in code and authorised here. The credentials stay with the platform, never in the repository.

One connection, used wherever the work happens

Pipelines

Ingestion assets and models load the service's data into your warehouse on a schedule, through the connection's HTTP client.

Ontology actions

An ontology action can call a connection, one record at a time: enrich a new lead, send an email, post a card to a chat.

The company agent

The company agent answers your team in Slack, Teams, WhatsApp, Telegram and email through the workspace’s connections.

Enterprise pilot

Want a connection built for you?

Our forward-deployed engineers build the connection, the pipeline that loads it and the app your team uses, in your own workspace, as code you own.

  • One solution, on your data, in your own workspace
  • First version live in two weeks
  • Parity proven before anything is switched off
  • Fixed scope and price, credited to your contract if you continue

Not ready for a pilot? Send the form anyway with your question. An engineer will reply, not a sales rep.

How the pilot works

Goes to our founder’s inbox. No sales queue, no newsletter.

Connect what your company runs.

Start a pilot

Our engineers build the first version on your data in two weeks, at a fixed price.

Or build it yourself with your coding agent:

curl -fsSL https://segmentstream.com/install.sh | sh

We’ll email you product updates, tips and onboarding help. Unsubscribe anytime.