Pipelines

Managed event filtering and webhook delivery for selected transaction, log, and block activity.

Pipelines is EVMKit’s managed event filtering and webhook delivery product for account-owned transaction, log, and block activity.

It lets you define transaction, log, and block filters, route resulting payloads to your own systems, and manage delivery behavior from one place.

Pipelines is useful when you want a managed integration layer between chain data and your own internal services. It keeps filters, destinations, routing, retries, and delivery records in one place instead of requiring a separate consumer, queue, and retry service for each integration.

You can work with the same pipeline resources in two ways:

manage them in the account dashboard UI
manage them programmatically through Pipelines API

What Pipelines does

applies account-defined transaction, log, and block filters
forwards resulting payloads to configured webhook destinations
applies delivery settings such as timeout, retries, and optional request signature headers
supports request signatures for destinations that use a webhook secret
keeps tests, delivery attempts, recent failures, and route state visible in one place

Core model

Pipelines is built around four account-owned resources:

sources define the filter configuration for chain data
destinations define the receiving webhook endpoint and delivery settings
routes connect one source to one destination in a selected region
deliveries record destination tests, route tests, and live delivery attempts

The dashboard UI and Pipelines API operate on the same sources, destinations, routes, and delivery history.

Supported source types

tx sources filter transaction activity by address and selector
log sources filter log activity by address, selector, and topic
block sources filter block activity by transaction count, graffiti, and coinbase payment

Delivery behavior

webhook destinations are validated when they are created or updated
routes can be paused or resumed without deleting the configuration
live deliveries can include X-Evmkit-Timestamp and X-Evmkit-Signature
delivery history includes destination tests, route tests, live attempts, retry state, and recent errors
routes keep recent operational state such as last success, last error, and consecutive failure count

Access model

Pipelines is available through authenticated EVMKit accounts.

Dashboard access starts after account authentication. Direct Pipelines API requests use your account API key in X-Api-Key. Active Pipelines access on the account is required for both access methods.

Accounts with Pipelines access can currently create up to:

5 sources, 5 destinations, and 5 routes at 1M / day
10 sources, 10 destinations, and 10 routes at 5M / day
10 sources, 10 destinations, and 10 routes at 10M / day
30 sources, 30 destinations, and 30 routes at 20M / day
50 sources, 50 destinations, and 50 routes at 60M / day and above