Skip to main content
PUT
UpdateEventPipelineAPI mirrors erdo_update_event_pipeline. Fields merge over

Authorizations

Authorization
string
header
required

An Erdo API key (erdo_api_...) or scoped token (erdo_token_...).

Path Parameters

pipelineSlug
string
required

Body

application/json
description
string
name
string
pipeline
object
purpose
string
request_schema
object
state
string
transform_js
string

Response

Success response

auth_config
AuthConfig is redacted on read paths — the plaintext verification secret · object

is stripped by toPipeline. The secret is surfaced only once, at create and rotate, via the Secret field below.

auth_mode
string
created_at
string<date-time>
created_by_user_id
string<uuid>
created_datasets
string[]

auto-created because they didn't exist yet. Populated only on the create and update responses (like Secret), empty on list/get — the creation must be visible to the caller, not silent.

created_from_thread_id
string<uuid>
description
string
endpoint_url
string
id
string<uuid>
last_updated_from_thread_id
string<uuid>
name
string
organization_id
string<uuid>
owner_artifact_id
string<uuid>
pipeline
object
purpose
string

user/agent-authored ones: "custom" (the default) or "page_events" (the per-page first-party analytics pipeline).

request_schema
object
secret
string

create and rotate responses (empty on list/get). It is a bearer-equivalent credential, so it is encore:"sensitive" (kept out of request traces).

slug
string
source_kind
string
state
string
transform_js
string
updated_at
string<date-time>
write_target_datasets
string[]

to (its dataset.write actions) — a convenience view of where the pipeline's output lands, parsed from Pipeline. Generic config, not tied to any use case.