uncut frigate
usually we store some information related to domain, but unfortunately I did not find any information on it?
Update subscriber preference
Endpoint
PATCH
/v1/subscribers/:subscriberId/preferences/:templateId
The above API is not allowing to save my own info?
past plover
hey @uncut frigate! 👋
the PATCH /v1/subscribers/:subscriberId/preferences/:templateId endpoint is used for something different, it allows you to update the subscriber preferences, for ex., if that subscriber should receive email from the particular workflow...
what you are looking for is PUT /v1/subscribers/:subscriberId, but unfortunately we only support these fields as far as I know: firstName, lastName, email, phone, avatar
could you please elaborate more about your usecase, and what you want to do with that information at the end?
uncut frigate
Hi @past plover
We want to store user preferences on notifications which is custom to our business logic. Was trying to check whether we could use any existing feature of novu to store the same without using additional data models at our end
granite acornBOT
@uncut frigate, you just advanced to level 2!
past plover
@uncut frigate so you wanted to decide like for ex., whether the notification should be send to the subscriber based on your business logic and for each of the workflow steps individually?
uncut frigate
I will save the info which helps to decide the "notification should be send to the subscriber based on business logic"
past plover
currently we do only allow for setting the preferences only on the channel type, like whether the subscriber should receive all notifications, or all emails...
uncut frigate
ok @past plover
past plover
@uncut frigate feel free to create the ticket on the Github, describing your needs and the use case 😉 we will look into
@next sun
uncut frigate
Sure Pawel