Skip to main content
A pipeline config defines where data comes from (source), how it is processed (transforms), and where it is delivered (sinks).

BeamConfig

The top-level object returned by all config endpoints.

CreateBeamConfigRequest

Request body for Create pipeline. Same as BeamConfig, without the server-set fields.

UpdateBeamConfigRequest

Request body for Update pipeline. Same shape as CreateBeamConfigRequest. The pipeline is identified by config_id in the URL path. Server-set fields (id, owner_org_team_user_id, organization_id, created_at, updated_at) keep their existing values and are ignored if sent.

PipelineConfig


Source

The Allium Datastream the pipeline reads from, identified by chain and entity.
For kafka sources, set only type, chain, and entity. The connection fields keep their defaults.

Supported chains and entities

Coverage expands regularly. For current availability, see the Datastreams catalog or call GET /api/v1/beam/sources, which requires a Beam-enabled organization.

Transforms

Transforms run in order. Two types are available. Omit uid when adding a transform; the server assigns one.
Set filters (redis_set_filter) are deprecated. New pipelines start with a JavaScript transform. Move your filter values to a dataset and check them with beam.contains() in a JavaScript transform instead.
Passes only records whose selected field matches a value in your set. Sets hold 10M+ values.
Common filter_expr patterns:Manage filter values with the filter values endpoints. Changes take effect immediately, with no redeploy.
Use lowercase values when filtering by addresses, labels, or symbols.

Sinks

A sink is where the pipeline delivers records. Each pipeline has exactly one sink, so sinks takes a single entry. Omit uid when adding a sink; the server assigns one. Five types are available:
Delivers to an Allium-managed Kafka topic. After deployment, the Allium App shows connection credentials and consumer code samples.
Need a different sink type? Contact [email protected].

IDs

When you create a pipeline, transform, or sink, omit id or uid and the server assigns one. When you update, include it to reference the existing resource.