SegmentStream

Connect the services your company runs.

21 ready-made connections, and 3 generic ones that reach any other API. A connection is declared in your workspace's code and its credential stays with the platform: pipelines and ontology actions call the service through it without ever holding the key.

ready-made
21
for any API
3
via API
39

Built in means a connection class for the service ships in the SDK. Via API means the service connects through a generic API-key, OAuth 2.0 or client-credentials connection, declared by your agent with the service's API address.

All integrations

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
Generic connectionsAny API with a keyBuilt inAny OAuth 2.0 APIBuilt inAny API with client credentialsBuilt in

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 Telegram through the workspace's Telegram connection.

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 join the waitlist for self-serve:

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

Self-serve opens to the waitlist first.