Skip to main content
POST
Put a routing rule on a destination

Headers

idempotency-key
string
required

Any client-chosen key, a uuid for example. Sending the same request twice with the same key has one effect and returns the same response twice; the same key with a different body returns 409.

Required string length: 1 - 255
Example:

"3f1b2c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d"

Path Parameters

id
string<uuid>
required

Body

application/json
name
string
required

The stable key of this rule inside the destination. Sending it twice updates the rule.

Required string length: 1 - 64
Example:

"newQualifiedLeads"

event
enum<string>
required
Available options:
new_engagement,
new_post,
new_qualified_lead,
run_completed,
account_marked,
account_mark_revoked
Example:

"new_qualified_lead"

audience_id
string<uuid> | null

Narrow to this audience. Null is everyone. Required for new_qualified_lead.

filter
object | null

Optional narrowing. Every key is optional and all of them are ANDed.

is_active
boolean
default:true
min_interval_minutes

How long this rule waits between two messages: 0 immediate, 60 hourly, 1440 daily.

Available options:
0
send_hour_utc
integer

The whole hour in UTC after which a daily send may go out. Only used at 1440.

Required range: 0 <= x <= 23

Response

The rule as it now stands.

data
object
required