Skip to main content
PUT
SetDatasetNotificationAPI replaces the recipient list for a dataset. An empty

Authorizations

Authorization
string
header
required

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

Body

application/json
after
string

notification waits for, so the email can say what that declaration found out about the row. Without it the two run at the same instant off the same write and the message is composed before the answer exists.

dataset
string
recipients
string[]

off: the underlying automation is removed rather than left disabled, so turning it back on later starts from the rows arriving then, instead of delivering everything that accumulated while it was off.

skip_when
string

get an alert email. The criterion is data, not policy: the platform judges each new row against whatever the caller wrote, with the MX lookup's answer supplied as evidence rather than acted on as a verdict.

timestamp_column
string

detected; set it when the dataset names that column unconventionally.

Response

Success response

after
string
dataset
string
enabled
boolean
job_id
string

run history through the automation surfaces.

recipients
string[]
skip_when
string
timestamp_column
string