Snooze Interaction
Hide one interaction until a deadline you set
snooze_until, after which it comes back on its own.
Interaction-scoped and self-expiring, which is the whole difference from dismiss: that one is person-scoped and permanent. Snooze is for “I have seen this, ask me again later”; dismiss is for “this person is not relevant”.
The three id fields identify the interaction. Take them straight off a row from the feed: rep_linkedin_id, target_linkedin_id, post_key.
Idempotent: re-snoozing overwrites the deadline. Omitting both snooze_until and days un-snoozes.
Authorizations
The API key you created on the API settings page of the Clustr app.
Body
The Clustr ID (per_…) of the competitor's salesperson. Their LinkedIn id (rep_linkedin_id on
the feed entry) also works.
The engaged person's Clustr ID (per_…). Their LinkedIn id also works.
The interaction's post_key, as the feed returns it.
The moment the snooze ends, as an RFC 3339 timestamp. Prefer it over days: you know the user's timezone, so you can turn "until Monday morning" into the right moment.
Snoozes for this many days from now, as a simpler alternative. snooze_until takes precedence when both are sent.