Crunchy API

Sure, but I think the concern is that a placeholder that has the `*_html`suffix would always return/render the HTML (properly escaped, etc). Such that there is no inconsistency in behavior of the placeholder across different usages.

For instance, why would `latest_public_comment_html` render as HTML in an email or other medium, but not in a webhook? If the API can return HTML as strings in the JSON response, why can't a webhook do the same? Like I said, it's just not intuitive given the naming of the placeholder.

I accept that this is the nature of how Zendesk has chosen to implement this behavior. But these kinds of inconsistencies is quite frustrating to work with as developers and engineers.

Yeah, it would be great to be able to reclaim my personal account so that I can change my name back! :-)

I stumbled on the following in the placeholder reference:

> Although placeholders can be in HTML format, when a placeholder is sent to a URL target or webhook, unformatted text is used to render the placeholder, not HTML. Also, placeholders won't work within code blocks. 

So, not a bug… but not intuitive either… if a placeholder is documented to return a particular format, then I would expect it to always do such. Not behave differently dependent of the context that it's used. Quite disappointing.

I'm seeing the same behavior. And the ability to send the raw HTML to a webhook as well. Perhaps this is a bug in the placeholders?

+1 - having a light user would be very useful and appreciated. Also, I would like to see the ability to setup some kind of no-login ‘service account’ that doesn't consume and admin or agent seat. Simply for use with custom integrations making API requests, etc.