You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no UX friendly way to get the transactional ID from UI. Currently only way to find out template IDs is by API call or in DB.
Some kind of user-defined unique identificator would be even better for transactional email template lookup, so it would be possible to switch templates via listmonk UI when needed without changing the backend code.
E.g. user-defined template property slug: string. api/tx params that require either template_id or slug.
The text was updated successfully, but these errors were encountered:
I'm also looking for a way to have a stable identifier for templates that can be used when sending a tx template via API call. In a typical setup the sender/user of the API needs to configure the id of a template somewhere and hence it would be good to have one or both:
see the id in the UI
have some alternative like a named identifier/slug that can be defined and is shown for a template
There is no UX friendly way to get the transactional ID from UI. Currently only way to find out template IDs is by API call or in DB.
Some kind of user-defined unique identificator would be even better for transactional email template lookup, so it would be possible to switch templates via listmonk UI when needed without changing the backend code.
E.g. user-defined template property
slug: string
.api/tx
params that require eithertemplate_id
orslug
.The text was updated successfully, but these errors were encountered: