chore: Include website_token key in the inboxes API response (#1765)
Many self-hosted instances require this key as a part of QA & maintenance. Since this key is not sensitive its better to send it as a part of the JSON response instead of having to use a regex to get it from the widget_script_tag
This commit is contained in:
parent
84560953ea
commit
27cf5ecdce
1 changed files with 1 additions and 0 deletions
|
@ -12,6 +12,7 @@ json.welcome_title resource.channel.try(:welcome_title)
|
||||||
json.welcome_tagline resource.channel.try(:welcome_tagline)
|
json.welcome_tagline resource.channel.try(:welcome_tagline)
|
||||||
json.enable_auto_assignment resource.enable_auto_assignment
|
json.enable_auto_assignment resource.enable_auto_assignment
|
||||||
json.web_widget_script resource.channel.try(:web_widget_script)
|
json.web_widget_script resource.channel.try(:web_widget_script)
|
||||||
|
json.website_token resource.channel.try(:website_token)
|
||||||
json.forward_to_address resource.channel.try(:forward_to_address)
|
json.forward_to_address resource.channel.try(:forward_to_address)
|
||||||
json.phone_number resource.channel.try(:phone_number)
|
json.phone_number resource.channel.try(:phone_number)
|
||||||
json.selected_feature_flags resource.channel.try(:selected_feature_flags)
|
json.selected_feature_flags resource.channel.try(:selected_feature_flags)
|
||||||
|
|
Loading…
Reference in a new issue