# Email image sources based on application.callback\_domain inside template

**URL:** <https://community.auth0.com/t/email-image-sources-based-on-application-callback-domain-inside-template/31751>\
**Category:** Get Help\
**Tags:** email-template\
**Created:** [October 3, 2019, 9:30am UTC](https://community.auth0.com/t/email-image-sources-based-on-application-callback-domain-inside-template/31751 "2019-10-03T09:30:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![michaeld](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/michaeld/32/12765_2.png) [@michaeld](https://community.auth0.com/u/michaeld)\
**Post date:** [October 3, 2019, 9:30am UTC](https://community.auth0.com/t/email-image-sources-based-on-application-callback-domain-inside-template/31751/1 "2019-10-03T09:30:13Z")

</div>

I would like to use the callback domain as base URL for image paths inside the Password Reset email template. This is due to the fact that there are a number of applications on my account, each deployed to a different location and having different logos.  
So far, I wasn’t able to access the application.callback\_domain property inside the template - even if I make sure that the password reset request is properly initialized with the application ID, using this value inside the template result in an empty string inserted in its place in something like: **\<img src=“{{application.callback\_domain}}/my\_logo.jpg”…**

Is this property accessible inside email templates? If it isn’t is there any suggested workaround (besides going **if…else** on application.clientID)?

---

<div class="post-metadata">

**Author:** ![StevenVerbiest](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/stevenverbiest/32/20581_2.png) [@StevenVerbiest](https://community.auth0.com/u/StevenVerbiest)\
**Post date:** [May 6, 2020, 9:06am UTC](https://community.auth0.com/t/email-image-sources-based-on-application-callback-domain-inside-template/31751/2 "2020-05-06T09:06:43Z")

</div>

I’m having the same problem and apparently the `{{application.callback_domain}}` does not work when you use the “Try” feature: [Broken redirect users to the first Allowed Callback URL - #5 by matt01](http://community.auth0.com/t/broken-redirect-users-to-the-first-allowed-callback-url/10310/5)

---

<div class="post-metadata">

**Author:** ![felipe.santos](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/felipe.santos/32/21865_2.png) [@felipe.santos](https://community.auth0.com/u/felipe.santos)\
**Post date:** [June 10, 2020, 9:10pm UTC](https://community.auth0.com/t/email-image-sources-based-on-application-callback-domain-inside-template/31751/3 "2020-06-10T21:10:00Z")

</div>

Were you able to make it work?

For me even sending the email programmatically {{ application.callback\_domain }} is empty.

---

<div class="post-metadata">

**Author:** ![mike-mw](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/mike-mw/32/24334_2.png) [@mike-mw](https://community.auth0.com/u/mike-mw)\
**Post date:** [September 18, 2020, 7:18pm UTC](https://community.auth0.com/t/email-image-sources-based-on-application-callback-domain-inside-template/31751/4 "2020-09-18T19:18:31Z")

</div>

Seems odd that if {{ application.clientId }} is available that {{ application.callback\_domain }} (the first value, if more than one is specified) is not - both are metadata at the same level.

The proposed workaround violates the DRY principle, which given Auth0’s developer audience is not the best direction to be taking the customer base in.

Is there a technical limitation lurking beneath?