Bynder is a cloud-based Digital Asset Management (DAM) platform that enables organizations to manage, share, and distribute their digital content from a centralized location.
With its user-friendly interface, the marketing team can create, find, and utilize digital assets such as images, videos, and documents efficiently.
By installing the Bynder app from the Contentstack Marketplace, you can use it within your stack to fetch and display digital assets from Bynder accounts within your entries.
Follow this step-by-step guide to install and configure the Bynder app within your stack.
To configure the Bynder app, you first need to create an account in Bynder. To do that, follow the steps given below:
To retrieve the OAuth credentials (Client ID and Client Secret), follow the steps:








To install the app in Contentstack, log in to your Contentstack account and follow the steps below:





Note
Note Multi Select is the default selected option.

You may get the Bynder login screen or permission screen for Bynder app whose credentials (Client ID & Client Secret) you have added in the configuration.

Once validated, you can use the Login Bypass and Enable Asset Tracker features.


Alternatively, you can set a configuration as the default by clicking the three dots on the top-right side of the configuration section and then selecting Set as Default.

Note At least one app configuration should be selected as the default.
Similarly, you can add multiple configurations by following the steps discussed above.

In the Confirm Deletion modal, add the configuration name and click Delete.


Warning
Note When you change the settings from All Fields to Custom Fields , and vice versa, any existing and newly added assets in the entry will store the data according to the updated configuration settings.

If you select Custom Fields , then the Bynder Keys drop-down appears. By default, extensions , id , name , previewUrls , type , files.webImage , databaseId , url , and additionalInfo options are already selected inside the dropdown. If you want to create a new key, click the + New Key Field option.

In the Add Bynder Key Path modal, enter the Bynder Key Path and click the Create or Create and Apply button to create a new key.


Additional Resource For more information on UI locations and webhooks, please refer to the Installed Apps guide.
To use the Bynder app within an entry of your stack, follow the steps given below:

There are two ways to use the Bynder app in your entry:

This adds Bynder in the custom field.

Additional Resource To set the configuration object, refer to the Set Advanced Config Object in Custom Field section.
You can see the Bynder app’s custom fields on your entry page as shown below:


Note



When the Advanced config is added for DAT, the Selector page drop-down for Multi-Select mode displays different transformations as options:

The selected transformation will be applied to all chosen assets.
Note
The assets you select get added to your entry in the thumbnail view.
To view the assets in the list view, select the List view option from the dropdown.

The assets you select get added to your entry in the list view.

Note The Open in Bynder function requires a one-time login for the first instance as the user is redirected to the Bynder dashboard.
Thumbnail View
List View

Additional Resource On saving the entry, saved assets are automatically tracked within your Bynder asset dashboard if the asset tracker is enabled. To view the asset usage, refer to the View Asset Usage in Asset Tracker section.
While adding the Bynder app in the custom field in step 3, you can set the configuration parameter during app installation in step 2.
Under Advanced properties, you have the option to set the Config Parameter for all entries of a particular content type. If you do so, it overrides the default app configuration you set at the time of app installation on the Configuration screen.
The key:value passed in the configuration object overrides the default app configuration settings.
{
"config_label": [
"configurtion-2"
]
}
locale Configuration Object:
{
"config_label": [
"configurtion-2"
],
"locale": {
"en-us": {
"config_label": [
"configurtion-3"
]
},
"fr-fr": {
"config_label": [
"configurtion-1"
]
}
}
}
DAT Feature Support for Multi Select Mode (optional) : For the multi-select DAT feature, you can apply predefined transformations ("thumbnail", "mini", "transformBaseUrl", "medium", "small", "large", "online") to assets by including them in the options list.
These transformations will only be applied if they are available for the selected assets. If a selected transformation is unavailable, the default transformation ("webImage") will be applied instead.
You can also apply custom transformations to assets through the transformation_options object by specifying a unique key name and providing the corresponding rule as its value.
{
"custom_settings": {
"dat_settings": {
"options": [
"webImage",
"mini",
"transformBaseUrl",
"medium",
"small",
"large"
],
"default": "webImage",
"transformation_options": {
"flip_rotate": "io=transform:flip&io=transform:rotate,angle:70",
"crop": "io=transform:crop,height:400,width:300,path:square"
}
}
}
}Additional Resource For more details on specifying rules for custom transformations, refer to the DAT documentation.
{
"custom_settings": {
"compact_view_options": {
"assetFilter": {
"showToolbar": true,
"predefinedAssetType": ["IMAGE"],
"predefinedTagNames": ["bottle_with_food"]
}
}
}
}Additional Resource You can include optional parameters in the compact_view_options object, except for attributes containing a period (e.g., portal.url ) or those with callback functions. For detailed description of these optional parameters, refer to the Bynder Compact View documentation.
{
"advanced": {
"max_limit":5
}
}
This adds Bynder in the JSON Rich Text Editor.

Additional Resource To set the configuration object, refer to the Set Advanced Config Object in JSON RTE Plugin section.
You can see the Bynder icon in the JSON Rich Text Editor field on your entry page as shown below:

Note



When the Advanced config is added for DAT, the Selector page drop-down for Multi-Select mode displays different transformations as options:

The selected transformation will be applied to all chosen assets.
The assets you select get added to your entry.

Note The Open in Bynder function requires a one-time login for the first instance as the user is redirected to the Bynder.

Additional Resource You can use alignment and inline asset features to edit the asset placement within the JSON Rich Text Editor field.
Note If you selected the Single Select File or Multi Select mode to add assets to your entry, you can view the information of the selected DAT derivative of the asset in their JSON object, in an additional parameter titled additionalInfo .
Additional Resource On saving the entry, saved assets are automatically tracked within your Bynder asset dashboard if the asset tracker is enabled. To view the asset usage, refer to the View Asset Usage in Asset Tracker section.
While adding the Bynder app in the JSON RTE Plugin in step 3, you can set the configuration parameter during app installation in step 2.
To add the Config Parameter in the JSON RTE field, click the Plugin Config gear icon on the app plugin selector page.
You can set the following validations for the JSON RTE field:
{
"config_label": [
"configuration-2"
]
}
DAT Feature Support for Multi Select Mode (optional) : For the multi-select DAT feature, you can apply predefined transformations ("thumbnail", "mini", "transformBaseUrl", "medium", "small", "large", "online") to assets by including them in the options list.
These transformations will only be applied if they are available for the selected assets. If a selected transformation is unavailable, the default transformation ("webImage") will be applied instead.
You can also apply custom transformations to assets through the transformation_options object by specifying a unique key name and providing the corresponding rule as its value.
{
"custom_settings": {
"dat_settings": {
"options": [
"webImage",
"mini",
"transformBaseUrl",
"medium",
"small",
"large"
],
"default": "webImage",
"transformation_options": {
"flip_rotate": "io=transform:flip&io=transform:rotate,angle:70",
"crop": "io=transform:crop,height:400,width:300,path:square"
}
}
}
}Additional Resource For more details on specifying rules for custom transformations, refer to the DAT documentation.
{
"custom_settings": {
"compact_view_options": {
"assetFilter": {
"showToolbar": true,
"predefinedAssetType": ["IMAGE"],
"predefinedTagNames": ["bottle_with_food"]
}
}
}
}Additional Resource You can include optional parameters in the compact_view_options object, except for attributes containing a period (e.g., portal.url ) or those with callback functions. For detailed description of these optional parameters, refer to the Bynder Compact View documentation.
To track the asset usage, enable the Enable Asset Tracker toggle during app configuration in step 2.
Once the asset tracker is enabled in the Contentstack Bynder app, you can view the asset usage statistics in the asset dashboard within the Bynder portal.
For any given asset, the app creates only one tracking instance per entry, regardless of how many times the asset is reused within different fields (Custom Field or JSON RTE) in that same entry.
The app automatically executes API calls to update asset tracking data in Bynder whenever you save the entry in Contentstack.