Configuration Guide for Bynder

Mediafly for Bynder lets marketers leverage their investment in Bynder’s Digital Asset Management (DAM) capabilities. Once configured, marketers continue to manage content in Bynder. When content is created or changed in Bynder, it is automatically pushed to Mediafly.

How it works

Synchronization between Bynder and Mediafly is done by a scheduled poller that queries the Bynder APIs and looks for changes in the DAM files. It uses the modified date time stored against the files to check for changes that need to be pulled across to Mediafly. Items that are copied across to Mediafly will include their Title, Description and Keywords (tags). The folder structure of child folders are maintained. The poller looks for changes every 5 minutes so changes to files should be seen in Mediafly within 15 minutes.

Configuration

To get you up and running with Mediafly, you will first need to create an OAuth App within Bynder. You can make this either an OAuth 1.0 or 2.0 app.

Please share with your Mediafly representative the following:

• The Bynder base URL for your tenant
• The Client ID and Client Secret for the Bynder OAuth app you have created
• If you prefer that we use OAuth 1.0, you will also need to create and send the Token and Token Secret

By default, we would start syncing all content. However, most customers prefer that we sync only a subset of content. Please let us know what rules you would prefer for:

1. What content to get, and
2. Where that content should go