How can i migrate from getThumbnail to public/image?

Business Case:

KPI to be measured

Bookmark this resource Follow

Ask a question

Was this article helpful? 0 out of 0 found this helpful

In the last few months, the getThumbnail web service that was commonly used to deliver image content without involving THRON player (html embed) has been deprecated in favor of the public/image web service.

This service, compared to the previous one, introduces a set of important advantages in the distribution of images:

  1. First of all, the delivered asset corresponds to the actual image converted by THRON into the appropriate formats, no longer to its thumbnail, with consequent benefits in terms of quality
  2. Secondly, the new web service is designed for assets' indexing by search engines
  3. Finally, the new service introduces the use of the sharing key (pkey) within the url. This allows you to keep track of each specific share and makes you capable of disabling or revoking it at any time.


To complete the migration of embeds associated with the previous web service, it is advisable to proceed in this way:

  • centralize all distributed images in the same branch of folders
  • enable a THRON Custom Application Manager in the root folder of the same branch
  • from the management panel of the application, enable a public share and store the provided pkey
  • change all the existing urls to the following structure:



  • clientId (mandatory): is the domain name used to access THRON. Usually the company name.
  • contentId (mandatory): the unique identifier of the content for which you want to extract the image, can either be the xcontentId or the prettyId.
  • pkey (mandatory): the sharing key previously stored.
  • divArea (mandatory): it is the desired dimension of the resulting image. If it is higher than the original image's dimension, no processing will be performed. If you want to get the highest thumbnail available you can set this parameter to "0x0".
  • prettyName (mandatory): the name to be used for the image for indexing purposes. You can put any name you want on this parameter, as long as it includes an extension, otherwise CMS libraries won't recognize it as an image asset. Use a name that is beneficial for your SEO strategy. Since the image might change in THRON over time, you are given the possibility to enter a custom name: because you don't necessarily want the URL of the image to change, thus preserving content indexing. 
    THRON will not consider the extension, if the source image is a png, THRON will return a png.


For a full description of all the parameters included in this web service we recommend you to read this article.

Was this article helpful?
0 out of 0 found this helpful

Have any question?

Open a ticket